Mastering Emacs

About the book

This is Mickey Petersen's book about GNU Emacs. It assumes you can open a file and move around, then works outward: configuring the editor, refining editing and navigation, and learning the facilities that make Emacs feel less like a program and more like a workspace you shape.

The premise is that Emacs rewards deliberate study. Petersen writes for readers who have used the editor enough to be curious about why experienced users stay, and who want explanations rather than a list of keybindings. The material leans on the editor's own documentation and on configuration as a practical skill, so the emphasis falls on understanding how pieces fit together before customizing them.

Emacs changes between releases, so treat the book as a guide to principles and workflows as much as to exact commands. The underlying model of buffers, modes, and configuration remains stable. Specific package names and defaults may not.

How to read it

Read with Emacs open. The book is most useful when each section prompts a small experiment in your own configuration, and least useful when skimmed as prose. Keep notes on what you change so you can undo it later.

Petersen's explanations are generally direct. The density rises once configuration and extension topics arrive, so expect to reread sections and consult the built-in help alongside the text. Readers who have never used Emacs should build basic familiarity first, since the book moves quickly past fundamentals.

Who it suits

This suits programmers, writers, and system administrators who already use Emacs and want to reduce friction in daily editing. It also helps readers who inherited a configuration and want to understand it rather than copy snippets. Anyone deciding whether Emacs is worth learning will get more from the book after some hands-on time.

Reading considerations

Package recommendations and version-specific details may be outdated, so check current documentation for anything you plan to adopt. The book teaches configuration, not a complete programming curriculum, and it will not suit readers seeking a gentle first introduction to the editor.