DEV Community

Discussion on: What do you look for in a Code Editor?

Collapse
 
jeremyf profile image
Jeremy Friesen

Three years ago it was: Open source (with sustained support), extensibility, and the ability to quickly load as my $EDITOR or $GIT_EDITOR.

But today, it's the above but it also needs to support my blogging and personal knowledge management. I've settled on Emacs after previously using Jedit, TextMate, Sublime, and Atom. In 2020 I chose to explore 3 editors: VS Code, Emacs, and Vim. It didn't take long to settle into Emacs.

README for Dotemacs

This is my Emacs configuration repository. It pairs with my dotzshrc repository. The install.rb script of the dotzshrc repository uses this repository. For implementation reasons, the emacs.d directory contains the init files that I link into my $HOME/.emacs.d directory.

For those curious, I wrote Why I Chose Emacs as My New Text Editor // Take on Rules.

The Structure

Below is the top-level directory:

> tree -L 1
├── README.org
├── deprecated-packages
├── emacs.d
├── lib
└── snippets
4 directories, 1 file

The files and directories:

README.org
This file.
emacs.d
A directory that contains files symlinked into $HOME/.emacs.d directory.
deprecated-packages
A directory of elisp-files. I have since moved towards a literate configuration style.
snippets
A directory of yasnippets I’ve created.

The emacs.d Directory

There are two “primary” files to consider in ./emacs.d:

configuration.org
This file is where I write my Emacs configuration with…