2 ms·
I've used Emacs since forever ago. I don't bling it out with Spacemacs, Doom, or any of the other things people install these days. I sound/feel like a boomer r
by bitwize 6y ago
I've used Emacs since forever ago. I don't bling it out with Spacemacs, Doom, or any of the other things people install these days. I sound/feel like a boomer railing against kids with their Minecrafting and Roblocks and social medias. But the point is, my Emacs workflow is reflective of the fact that I don't use Emacs because it gives me some huge needed leverage over the act of writing code. That is relatively straightforward, and the plain Emacs bindings, once learned, are more than suitable to the task.
Rather, I use Emacs because of a combination of pain points that it simply handles better than other editors, that add up to a significant advantage:
* Emacs does electric indent "right". Other editors will attempt to indent automatically, but the tab key always means "insert tab", not "indent this line to its computed indent level". This alone makes it more pleasant to use than most "modern" code editors.
* By default, Emacs will help you match paired delimiters (parens, brackets, quotes, etc.) but will not insert closing delimiters. This saves me that awkward experience of typing out a code block, parameter list, or string constant, only to find that I now have mismatched delimiters because I didn't realize I was supposed to cursor over the closing delimiter my editor oh-so-helpfully provided rather than type it myself. Except some editors just cursor over the closing delimiter if it senses that you're typing the delimiter at point. Some don't, though, and it's hard to remember which is which!
* I work a lot in Lisp, and Emacs is better suited to handling Lisp code than most other editors.
* Emacs is an immensely useful programming environment. There are applications like Magit and Org-mode built on top of Emacs that are just stupid useful workflow grease. On top of that, if there are pain points in my workflow, coding something up in Emacs Lisp to handle them is incredibly easy and straightforward, and I can evaluate and test my code right in my running Emacs session. Contrary to popular belief, Emacs integrates well with Unix tooling; Unix tools can be easily plumbed together with Emacs buffers, enabling you to use Emacs as a kind of "super-shell" to capture, move, examine, and massage data.