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

The title is a Scott Meyers homage, and the essay admits at the close that it began life as "50 Specific Ways" before Steve, a little over two hours into a single late-night sitting, gave up and edited the heading down to ten. What survived is a tutorial with an unusually high contempt-per-tip ratio: the mouse is a "cache miss," IDE users are amateurs "pawing at their instrument," and skeptics get sent off with "I think your Eclipse just finished launching, so you can get back to work now." The literal instructions are museum exhibits by now — swapping Caps-Lock means typing hex into the Windows registry, and the Mac fix is a "little scary" custom keyboard driver for OS X Panther — but the habits underneath them, Control on home row and incremental search as the primary way to move a cursor, are still what veteran Emacs users teach new ones.

The section worth slowing down for arrived a year after publication. A reader hated the entire essay over the turn-off-your-menus tip and invoked "countless studies" proving the mouse faster; Steve answered with actual stopwatch trials, a partial concession on scrollbars backed by the U.S. Navy's preference for analog gauges in reactor plants, and an admission that exactly one editing operation really is faster with the mouse. For a piece this smug, it is unusually willing to publish its measurements, including the ones that go against it.

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.