81–89 of 89 posts
Earlier quoted context omitted.
Launch it as a daemon and instantly connect via emacsclient.
I should do that, but it seems like a Band-Aid solution to the real problem which is poor performance.
Earlier quoted context omitted.
I’ve never understood the load time argument about IDEs, I probably restart my IDE whenever I do os upgrades every other week or so. This is true when I use IntelliJ, Emacs, or VS Code. Any of these could take 30s or longer to start for all I care. The issue with VS Code is that it’s more memory hungry than google chrome. More than once I’ve caught it using half a gig of memory, with various instances of flow using u…
I prefer using one editor for every task. This means both coding and quick config edits or jotting down notes. So while I often keep an instance up for hours, I also open and close it frequently enough that load time is enough of an issue.
Emacsclient would solve this issue for you though.
Earlier quoted context omitted.
>> I end up deleting half of the file's contents. Are you sure you're not using vim?
Nah, vim's modal. True, one of those modes is 'break everything', but the other mode is 'beeping furiously', so I generally notice I'm not in emacs pretty quickly.
It is well known that users may press these keys by mistake, while falling asleep on their keyboard. Therefore, vim beeps to keep them awake and avoid trouble.
Earlier quoted context omitted.
Vim. Vim's command-line is more alien to the last 4 or 5 gui-bred younger generations of programmers. Learning to master it is therefore more of a badge of hounour, and for that, more sought-after, than learning to master Emacs. Personally, I'd rather have Vim, but with Emacs-Lisp as a scripting language. That would rock.:x
Look into Evil.
Earlier quoted context omitted.
I prefer using one editor for every task. This means both coding and quick config edits or jotting down notes. So while I often keep an instance up for hours, I also open and close it frequently enough that load time is enough of an issue.
I personally do not use one editor for everything. To each their own. Emacsclient would solve this issue for you though.
Earlier quoted context omitted.
I think emacs already does that fine
have you actually used emacs on a cpu made in the last 20 years and found it to be slow? compared to vim or bash, it is cpu intensive. compared to any of the graphical apps that come with a mac, it is easier on the cpu (and on RAM).
1. Large files
2. Anything synchronous and blocking that takes a little too long can be frustratingly slow. This often isn’t entirely the fault of emacs (e.g. if it is slow because an external program is slow) but async isn’t done for everything so sometimes things block and you can’t do anything while they are working. This is particularly annoying if the external program provides eg auto-completion
3. Running a macro a large number of times
4. Building the completion list when finding files (I think this is a combination of an issue with the extension for finding files and how it reads a directory and just reading a very large directory over nfs)
5. Sometimes it becomes slow enough that the visual lag between key press and character-on-screen is annoyingly large
Can I get a quick vim vs emacs usage vote here? Not looking for a war. Just a usage vote. I will try and update results. Feel free to reply with your daily hours too Results below- small sample but makes me wonder about stack overflow survey about vim being thrice as used as emacs. I am a very loyal vim user but I would wager that those results were influenced by the occasional vim user. What are others thoughts on t…
Can I get a quick vim vs emacs usage vote here? Not looking for a war. Just a usage vote. I will try and update results. Feel free to reply with your daily hours too Results below- small sample but makes me wonder about stack overflow survey about vim being thrice as used as emacs. I am a very loyal vim user but I would wager that those results were influenced by the occasional vim user. What are others thoughts on t…
Emacs. Vi is awesome — it really is — and vim is neat too, but I prefer an entire operating environment. And Lisp. And man-centuries (man-millennia?) of usability improvements.
Earlier quoted context omitted.
have you actually used emacs on a cpu made in the last 20 years and found it to be slow? compared to vim or bash, it is cpu intensive. compared to any of the graphical apps that come with a mac, it is easier on the cpu (and on RAM).
I use emacs basically all day and so my comment was partially in jest. I find the following things to be slow: 1. Large files 2. Anything synchronous and blocking that takes a little too long can be frustratingly slow. This often isn’t entirely the fault of emacs (e.g. if it is slow because an external program is slow) but async isn’t done for everything so sometimes things block and you can’t do anything while they…