3 ms·
> Learning emacs and vim from decades old documentation is quite a journey. Can't speak for Vim, but the Emacs documentation has hardly succumbed to the sort o
by throwanem 11y ago
> Learning emacs and vim from decades old documentation is quite a journey.
Can't speak for Vim, but the Emacs documentation has hardly succumbed to the sort of obsolescence your description of it implies. (It's also built in to the editor, and reachable via M-x info.) You might want to take a look at it, before you go on consigning novices unfortunate enough to heed your bad advice to the hell that is Stack Overflow. (And if you're going to point people in even that general direction, at least point them at Emacs SE, which unlike SO isn't overrun with garbage and lies.)
- _delirium 11y agoI agree, for emacs, I find the official documentation nicer to use, because it's about the version I'm actually using, while a lot of the web stuff is years out of date, whether it's in blog posts, StackOverflow, or EmacsWiki. This matters for some things more than others of course, since some stuff hasn't changed in years, and other things have been overhauled more recently (like packages).
- bigmanwalter 11y agoEmacs documentation is good for exploring modes, but I found StackOverflow way better when I have no idea what the name of the feature I'm looking for even is.
- throwanem 11y agoApropos and describe-{function,variable,key} argument expansion can help a lot here.
- marklgr 11y agoVim documentation is solid too: it's included in the editor (like Emaces), and you can look things up with `:help` org `:helpgrep`. There are both tutorials, end-user-oriented pages and comprehensive references. IMO, Emacs is still slightly ahead with its C-h a/f/c` commands, but both projects boast quite good documentation.