9 ms·
I'm pretty happy with neovim nowadays... With Neomake, I get enough "IDE" features that I can stay productive, and it's fast enough that I don't miss Emacs' sup
by chousuke 10y ago
I'm pretty happy with neovim nowadays... With Neomake, I get enough "IDE" features that I can stay productive, and it's fast enough that I don't miss Emacs' superior tools.
I don't think I can ever get used to a non-vi editor (I feel uncomfortable even browsing without vim-style shortcuts thanks to pentadactyl/vimfx), but there is one for Emacs so that is not a show-stopper.
I did in fact try Spacemacs for a while, and wanted to like it, but in the end I couldn't get rid of my muscle memory to just start new editors in terminals all the time, and Emacs' daemon mode had stability issues for me, so it wasn't very usable: either it'd crash at times or startup would be unusably slow.
Muscle memory is a powerful thing. I had to alias "vi" to "nvim" just to be able to use neovim...
- pmoriarty 10y agoNeither neovim's or vim's ecosystem is primarily (or even significantly) Lisp, though. A fully Lisp ecosystem is one of emacs' greatest attractions, and one that neither vim nor neovim is likely to ever achieve.
- fmoralesc 10y agoNot with that attitude ;) https://github.com/adolenc/cl-neovim https://github.com/adolenc/cl-neovim
- pmoriarty 10y agoYeah, you can script vim in Lisp (Scheme to be more precise). That's been possible for a long time, with mzscheme. But virtually no one ever does. The vim ecosystem is overwhelmingly vimscript. Python is gaining popularity, and if anything a mainstream language like that is likely what the neovim ecosystem will eventually wind up consisting of. Not Lisp. Contrast that with emacs, where it's Lisp, Lisp, Lisp, and will continue to be Lisp for the foreseeable future (with a detour to Scheme possible in the long run).