My Emacs configuration
b941ea25 — Dominik Kellner 6 months ago
Update screenshots
adb16c05 — Dominik Kellner 6 months ago
Add `iy-go-to-char`
e1498ded — Dominik Kellner 6 months ago
Bind `company-complete` to a more convenient key


browse  log 



You can also use your local clone with git send-email.

#My Emacs configuration

Simply put, this is my configuration for Emacs. To a greater degree, it is an ongoing attempt to discover how my ideal computing environment should look like.

There are many others like it (see "Inspirations" at the end of this file). As one's editor configuration is naturally a matter of personal taste and expectations, don't try to use this one as it is. Read some sections, learn about my way of doing things, cherry-pick the parts you enjoy, and keep hacking!

To read the configuration, I recommend opening init.org in Emacs.

Here are some screenshots to give you an idea of how it looks like:

Dark theme (gruvbox-dark-hard)

Light theme (gruvbox-light-hard)


In its current version, my configuration tries to achieve the following goals (in this order):

#No distractions

Very few things should be important enough to arbitrarily redirect your attention. That's the reason why there are no notifications, not even a clock. Yet all information I need is just one key binding or M-x away.

#Ergonomic and consistent controls

To improve typing ergonomics in general, I'm using an ergonomic keyboard layout called Neo. This puts frequently used keys in the home row and adds more modifier keys, which make writing special characters easier.

To reduce typing of key-chords, I'm using a modal editing mode called Boon. Since very recently this provides idiomatic key bindings (e.g. you can use n and p for next-line and previous-line). This also plays nicely together with special Emacs modes who already use those keys for navigation, e.g. org-agenda-mode.

#State-of-the-art development experience in selected languages

Setting up Emacs to support the programming language of your choice is one of the most fun but also hardest tasks. Usually there are at least a dozen different packages to consider, try out and integrate into your workflow.

I'm trying to unify different language-dependent solutions using Nix, direnv, lorri and LSP. For Python and Rust this works reasonably well.