Scala developer. Loves functional programming at the type level.
Reads books, plays Squash and builds Lego.
It turns out that writing programs in Emacs Lisp is more intricate than it seems at a first glance. Emacs decades-long history as interactive application have left deep marks in Emacs and Emacs Lisp, which make independent noninteractive scripts surprisingly difficult.
This article shows you all the pitfalls around non-interactive Emacs Lisp scripts.
Show Magit’s status buffer fullscreen with
How to Tell Emacs where buffers should pop up with the almighty
Why you should use package.el to install Emacs extensions.
In the past I used to keep my Emacs configuration completely in a single
init.el file. For a long time this worked quite well, but of late my
configuration became increasingly messy: Package configuration was mixed with
utility functions, key bindings, and even larger code for entirely new features.
Needless to say that my init file was in dire need of a very thorough cleanup.
I had heard a lot of good things about John Wiegley’s use-package macro, and
in the days after Christmas I decided to sit down and try to refactor my Emacs
use-package. The result was very pleasant, and much better
than I had dared to hope.
There’s not a day in which I don’t find a new gem for Emacs. Today it’s the
bug-reference-mode. This fancy little thing turns issue references
in text into clickable buttons that browse the corresponding issue in a bug
tracker. I discovered it via the bug-reference-github package, which
automatically configures the mode for files in Github repositories.