2 ms·
So what you posted here...this is what I want to see in the OP's otherwise well-intentioned guide. I can say "yes" to a lot of those things, and "maybe" to the
by danso 12y ago
So what you posted here...this is what I want to see in the OP's otherwise well-intentioned guide. I can say "yes" to a lot of those things, and "maybe" to the others...Don't get me wrong, I love learning new things, especially languages...but in this case, we're talking about a tool that is critical for me to learning other things...when writing an evangelism guide, the saying, "show don't tell", is even more urgent.
That said, I'm going to hold off of emacs at the moment. My goal has still been to learn vim :)
- dublinben 12y agoI think the learning curve of Emacs is much easier than vim. You still have a GUI that exposes most of the important functions, and can learn the key bindings as you go. You can start using Emacs for basic editing without actually knowing how to "use" it.
- poolpool 12y agoLike gvim or macvim.
- fearandclothing 12y agoI remember back before I knew how to use vim (I was an Emacs guy then) it was a nightmare when I would forget to set my EDITOR variable and get dropped into vi to write commit messages; I couldn't edit my way out of a paper bag and could never remember how to exit without saving, though after a while ':q!' became the only vim command I knew.
- msg 12y agoAlso, and this is weird, you can get vi bindings in emacs through editing modes like viper-mode or evil. So if you want, in emacs you can have both. In contrast, you will never see emacs inside of vim.
- qu4z-2 12y agoHah! The way vim extensions are going you'll have emacs-in-vim soon enough. Not that I think it's a good idea, mind you. People spend too much time in vim as-is. (it's fine for emacs; that one's essentially a desktop environment)