2 ms·
Huh, my experience is the other way around. The "killer" of vim is the control scheme, and evil mode ports that over very faithfully to emacs. Then you get the
by kqr 4y ago
Huh, my experience is the other way around. The "killer" of vim is the control scheme, and evil mode ports that over very faithfully to emacs. Then you get the best of both worlds. Why would you use vim other than in very barebones environments where you cannot access your own config?
(I also don't see how tramp is an issue -- it opens up workflows I wouldn't even have access to without it!)
- softirq 4y agoWhy would I want to run an emacs layer adding more latency to my work to turn Emacs in to Vim when, as I said, I can do everything in Emacs I can do in Vim. > (I also don't see how tramp is an issue -- it opens up workflows I wouldn't even have access to without it!) Because it will randomly freeze and it's single threaded, it's slow, and it's also not novel. Vim can also edit files over SSH, VSCode can run itself remotely.
- School-Cotton 4y ago> I can do everything in Emacs I can do in Vim Can you immediately jump to the source code associated with any key binding, read it, debug it, modify and reload it, etc., regardless of whether it comes from the base distribution or a plug-in? For me that’s the killer feature of emacs.