High CPU/memory usage and abnormally large savehist file?
I would guess that's a result of one specific persistent variable getting enormous (it just seems less likely that you would have multiple instances at the same time), but if you've deleted the file you can't see which variable it was. You can always rename the file rather than deleting it, so that you can make Emacs happy again, but still analyse the data. If you recreate this situation, and the
ripgrep - ã‚ã®The Silver Searcherを超ãˆãŸè¶…高速ファイル検索ユーティリティ | ソフトアンテナブãƒã‚°
ファイル検索ユーティリティThe Silver Searcherã®é€Ÿåº¦ã¨ã€GNU grepã®å¤šæ©Ÿèƒ½ã•ã‚’ä½µã›æŒã¤æ–°ãŸãªãƒ•ã‚¡ã‚¤ãƒ«æ¤œç´¢ãƒ¦ãƒ¼ãƒ†ã‚£ãƒªãƒ†ã‚£ã€Œripgrepã€ã€‚Rustã§ä½œã‚‰ã‚ŒãŸã‚ªãƒ¼ãƒ—ンソースソフトウェアã§ã€Windows / Mac / Linux用ã®å®Ÿè¡Œãƒ•ã‚¡ã‚¤ãƒ«ã‚’ダウンãƒãƒ¼ãƒ‰ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ ripgrepã®ç‰¹å¾´ã¨ã—ã¦ã¯ã¾ãšæ¤œç´¢é€Ÿåº¦ã®é€Ÿã•ãŒä¸Šã’られã¾ã™ã€‚Linuxカーãƒãƒ«ã‚½ãƒ¼ã‚¹ãƒ„リーã«å¯¾ã—「[A-Z]+_SUSPENDã€ã¨ã„ã†å˜èªžã‚’検索ã—ãŸå ´åˆã€é«˜é€Ÿæ¤œç´¢ãŒå£²ã‚Šã®The Silver SearcherãŒ0.753så¿…è¦ãªã®ã«å¯¾ã—ã€ripgrepã¯0.245sã¨ã•ã‚‰ã«ãã®ä¸Šã‚’è¡Œã£ã¦ã„ã¾ã™ã€‚ 機能é¢ã§ã¯The Silver Searcherã¨åŒæ§˜ripgrepã‚‚å†å¸°æ¤œç´¢ã‚’デフォルトã§å®Ÿè¡Œã—ã¾ã™ã€‚ .gitignoreç‰ã§æŒ‡å®šã•ã‚Œã¦ã„るファイルやã€éš ã—ファイルã€ãƒã‚¤ãƒŠãƒªãƒ•ã‚¡ã‚¤ãƒ«ãªã©ã‚’無視
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
処ç†ã‚’実行ä¸ã§ã™
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
ripgrep.el : ã€agよりã€ãšã£ã¨ã¯ã‚„ã„!!】超音速grepã¨Emacsインターフェース(Windows安心)
{{#tags}}- {{label}}
{{/tags}}