5 ms·
Which use cases are slow for you ? you used it on large code base or parsed cpp source ? A quicker emacs would be neat, but most of the time emacs gets speed f
by agumonkey 9y ago
Which use cases are slow for you ? you used it on large code base or parsed cpp source ?
A quicker emacs would be neat, but most of the time emacs gets speed from flexibility (it might be slow but I can automate something) and design decision (magit for instance blows 99% of the fastest git interfaces)
ps: one part that realize is that I don't like emacs daemon, and even curated my setup on windows (probably the culprit) takes a few seconds. It's not slow but often I want a buffer right away so I use notepad u_u; stupid I know.
- kqr 9y agoAlso worth mentioning that whatever is slow, profile it to find out why. Sometimes only the smallest tweak is necessary to get it up to speed again. (Different tweaks for different configurations, so can't be a default.) For interactive use, profiling is as simple as M-x profiler-start, doing what causes the slowdown, and then M-x profiler-report.
- agumonkey 9y agoGood point, emacs has a lot of tooling (edebug and tracing too) but it's rarely demonstrated, and since emacs is so large.. In my case there's nothing slow but IO, I should try on another windows laptop with a faster SSD (mine is low grade) to see what is what.
- confounded 9y agoWith an Emacs server/daemon, it loads faster than Vim for me.
- agumonkey 9y agoI would happily agree but I lost the one emacs and 119422 buffers mindset. I get lost in my own shit. I should spend time improving my ibuffer grouping but even then.. I like the idea of pop, edit, kill (which causes my harm).
- alexhutcheson 9y agoIf you bind crux-kill-other-buffers[1] to a key, you might end up with a workflow you're happy with. [1] https://github.com/bbatsov/crux/blob/master/crux.el#L496 https://github.com/bbatsov/crux/blob/master/crux.el#L496
- tmalsburg2 9y agoMy solution: Accept that there will be dozens or even hundreds of buffers and use helm-for-files (which lists recent buffers first) to switch between the buffers I care about at any given time. Works really well.
- agumonkey 9y agoI think I need some fancier categorization like day columns, and content tags. But I'll keep your suggestion in mind
- twblalock 9y agoI've noticed that pasting large amounts of text (> 1000 lines) can make it grind to a halt for several minutes. I don't know if it's due to the mode I'm in.
- kaushalmodi 9y agoMore than the number of lines, it's the number of characters on a single line that causes the slowdown. Thankfully I don't have a real usage scenario where I handle thousand character line files. I can edit multi-thousand line (5k+) Org documents just fine. So it's probably the major mode or some minor mode(s), or a combination.
- tonyarkles 9y agoIn my experience that's often due to major modes that try to format and syntax-highlight on the fly. Keep in mind that some forms of pasting are really equivalent (from Emacs' PoV) to a crapton of keystrokes being entered. Anyway, the workaround I have for the occasional time I have huge things to paste is to switch the buffer to fundamental-mode before pasting, and then switching back. As a curiosity, what kind of things are you pasting that are that big?
- agumonkey 9y agoFew editable systems are happy with 1K lines. I remember a discussion where only one editor was happy dealing with that, all other became sluggish.
- barrkel 9y ago1k lines does not stress many editors. It only stresses emacs when the major mode is doing lots of stuff to highlight and format. I regularly used other editors on C files with 30k+ lines, 15 years ago when machines were slower. Emacs' real weakness is an over-reliance on regexes for highlighting and poor integration with sources of semantic and symbolic information for richer highlighting, editing and browsing. That, and synchronous operations for the same.
- 9y ago