But alas, emacs is just too slow during startup for my workflow. I use it with clojure but only because of Cider.
You do have to get into the habit of exiting by closing the buffer or the frame instead of quitting Emacs.
Plus I haven’t figured out how to keep my buffers organized. When I’m working on project x, I don’t want to see project y buffers. I’m sure there are many plugins for that too, but the state gets corrupted over time and stuff I use quits working.
I much prefer separate instances for separate work, and nvim or vim start from scratch faster than an emacsclient connects.
Sticking to vanilla Emacs undo is supposed to be more reliable.
- magit. unbelievable.
- org mode. vimwiki pales in comparison
- best vim emulation I've used
- impressive operating system :)
- configuration is awesome. doing literate org mode configuration with org babel.
- lisp is cool.
- haven't gotten comfortable dealing with "projects" yet, navigating files feels awkward.
- doesn't feel quite as good as an editor as vim, but better than anything else out there.
- no flutter mode
- elm integration not quite as nice as I'd like
it feels like I'll get over the cons.
What makes navigating files in vim so much better?
Vim was my primary editor for decades, but I was never particularly impressed with its file-navigation plugins, and mostly used the shell for file navigation. Emacs is really no worse in this regard, from what I can see. It has packages which are clones of or similar to vim plugins like NerdTree and the like (which I don't like myself and don't use, but they're there if that's your thing), and it has a bunch of other ways to navigate files -- like doing so from the minibuffer using counsel-find-file, or from dired, or from within a shell running inside Emacs, etc.
"doesn't feel quite as good as an editor as vim"
In what way? Have you tried evil? It makes Emacs 90% like vim, in my experience, and I rarely miss anything from the vim world myself (though, honestly, there are a handful of things that would be nice to have.. but not nearly enough for me to contemplate switching back to vim).
P.S.: I also happen to be a vi user.
Just because it takes time and effort to master and fine-tune a tool, required process does not render the tool impractical. Au contraire - it makes that tool the best suited for the task.