Effective Emacs — cover art: a wise old wildebeest (the GNU mascot) in a deep-oxblood waistcoat sits at a Victorian writing desk, hands resting on a small brass-keyed keyboard, ten editing tools laid out in a neat row beside him, a dusty toy mouse forgotten on the floor.

2005 · Drunken Blog Rants · Tutorial

“The key to understanding Emacs is that it's all about efficiency, which includes economy of motion. Any trained musician will tell you that economy of motion is critical to becoming a world-class virtuoso. Using the mouse is almost always the worst possible violation of economy of motion.”
— From Effective Emacs, January 2005
Read the essay

© 2005 Steve Yegge. Originally published at Drunken Blog Rants.

Author’s note

In 2006, all the best engineers used Emacs. Practically every respondent to the Stiff Asks interview used Emacs, except for James Gosling... who co-invented Emacs. It was the light saber of editors for those who took the time to delve into it.

Today, this post is essential reading if you have a time machine. Otherwise, it's not going to help you, because as of 2026, Emacs is no longer a real differentiator. Even I find myself using only a tiny fraction of its power anymore, like using a Lamborghini SUV for grocery shopping.

AI Notes

Ten-tip tutorial framing Emacs as a virtuoso's instrument: economy of motion, mastered the way a concert musician masters a phrase, with the mouse as the violation. Every tip flows from that frame. Swap Caps-Lock and Control so the pinkie never leaves home row. Rebind M-x to Ctrl-x Ctrl-m because Alt is awkward and unreliable over ssh. Prefer backward-kill-word to Backspace, because at 50 wpm killing the word and re-typing is faster than painstaking correction. The middle covers incremental search as the primary navigation tool, the buffer-window-frame distinction, and the case against menus and dialogs; the closing tips turn to regular expressions and the surgical text-manipulation commands — transpose-words, keyboard macros, kill-line semantics — that distinguish a power user from a wizard.

The practitioner's manual in a lineage that runs through My .emacs file, The Emacs Problem, and eventually Emergency Elisp, js2-mode, and Ejacs.

Related listings

  • 2005

    My .emacs file

    Same year — the companion piece, showing Steve's actual config: a tiny .emacs file that loads a directory tree of ten thousand lines of personal Elisp and a quarter-million lines of community Lisp.

  • 2005

    The Emacs Problem

    Same year — the philosophical counterweight. Effective Emacs is the practitioner's manual; The Emacs Problem is the architecture critique that explains why so much of Emacs still feels hand-cranked in 2005.

  • 2008

    Emergency Elisp

    Three years later — once you have read Effective Emacs and started changing key bindings, this is the cookbook for writing the Elisp that backs them.