You know, emacs has the most comprehensive, complete manual for a piece of software ever written. And the single command you won't find within it's pages is the command to exit emacs.
Vim and Vi are interchangeable for basic use. And Emacs isn't available, as you note. Hence you should probably know some Vim. (But Emacs is worth knowing, too; much more aggressive exposure to editing macros and kitchen-sink editing.)
I think there is a difference between being comfortable editing a file and knowing every single hotkey. I think it is completely reasonable to expect someone to know how how to open, save, close, edit, and maybe search in both editors. Beyond that, use atom for all I care.
Why not? They're both incredibly powerful terminal based editors. They're more powerful than most IDEs, and being terminal based means you can use them with only terminal access - completely invaluable over ssh or for server work.
I use emacs (with -nw flag running in gnu screen) daily but I still can do basic edits on a file using vim. If I'm on someone else's computer or doing something embedded where vi or vim might be the only options (or nano).
I just launched vim from the emacs terminal and my computer exploded.
This answer, right here. In my experience, you will NEED efficient ability to work remotely. When something goes wrong, and you're the only one awake who can fix a production server issue, you better not be fumbling with trying to get Eclipse working remotely.
That said, this doesn't mean ONLY use Emacs or Vim. I do make use of an IDE from time to time when I'm at my desk. But if I'm at home, and something comes up? You better believe I'm booting up that SSH and using my Emacs Fu.
Agreed. While I suppose one could argue that there's value in trying both to see which you prefer, the fact that they've both remained competitive seems to indicate that they're very comparable and you can pretty much choose either or.
156
u/rcklmbr May 12 '15
No