3 ms·

I haven't gotten around Emacs yet. I'm on a MBP and the Emacs controls are bothersome (to say the least) compared to Vim. I tried using Spacemacs, but it kind o

• gkya 11y ago
  These are my suggestions: Take Emacs as a lisp machine, a working environment, a framework. Then start building it up to your liking. A bit of Emacs lisp knowledge is essential, and it is an easy language, though with rough edges. With org, be experimental and incremental, don't try to create a perfect system from day one, start small and tame it to your habits and tendencies. But get used to the capture+refile flow (see info). I can't comment about evil, but I do not really feed the need for vi-style editing. Typing speed is not the bottleneck for me. When I type prose, I use Emacs standard bindings + visual line mode. When I program, and nowadays I program exclusively Emacs lisp, and exclusively for my needs, I use paredit. I feed good with these, and I do not feel a need for more speed. But everybody is a bit unique in their needs, so if you'll feel better with evil, go for it. My last suggestion will be that of avoiding things like Prelude and SpaceMacs. Steal from them, but build your own config yourself. Apart from this, I always use a stable release of Emacs and always check in to git the packages I use, so that I will not have to depend on 3rd parties for my setup. My .emacs.d is simply vital to me. Edit: about controls, mapping caps lock to ctrl is a life saver, though I do not know well the mac keyboard.