Why Emacs Still Feels Like Home
Emacs remains my favorite editor because it lets me inspect the tool, change the tool, and eventually build new behavior inside the tool.
Draft translated from an Org note. The original had a lot of package inventory and code snippets, which are summarized here instead of copied verbatim.
The core appeal is transparency. Emacs does not force me to accept a sealed workflow. When something feels slow, awkward, or missing, there is usually a way to trace it, understand it, and change it.
How my configuration is shaped
I split the configuration into an early startup phase and a main package phase. The early layer focuses on startup behavior, garbage collection, native compilation, and UI stripping. The main layer handles the actual working environment: completion, themes, version control, notes, terminal tools, and AI integrations.
What matters more than package count
The interesting part is not how many packages I use. It is the interaction between them:
- a modern completion stack built around Vertico, Consult, Orderless, Corfu, and Embark
- version control through Magit and related tooling
- note-taking through Org
- language tooling through built-in systems and Tree-sitter integrations
Why I keep investing in it
Emacs keeps rewarding deliberate attention. The more clearly I understand the editor, the more it becomes a durable part of my workflow instead of a temporary preference.