A Google Alert on "emacs" surfaced a Reddit post this week titled, in full: "After snap updated version 31.1 without asking me I get function undefined error for many of..." — cut off at the title, the body unread, but the title alone is the whole story.
Projectile ships with sensible defaults for switching projects and listing files, and most of my config leaves packages at their defaults unless something specific needed to change.
My Emacs config loads two separate linter frameworks in the same file, both fully configured, both actually running: flymake and flycheck. They're not doing the same job for different languages, and neither one is dead configuration left over from a migration that didn't finish.
Seven packages in my Emacs config are fetched with package-vc-install instead of the ordinary archive-based use-package foo :ensure t: auto-package-update, powerline, centaur-tabs, lsp-mode, php-mode, dap-mode, and smartparens-mode, each cloned straight from its GitHub repository
Two different lines in my own Emacs config call the exact same function twice, in the exact same file, a few lines apart. Neither one breaks anything. Both are worth understanding, because they demonstrate two different things about what use-package actually guarantees — and neither one is what I assumed before I went looking.
My Emacs config has three completion frameworks installed and configured: auto-complete, company, and corfu. Only two of them are actually doing anything.
init.el on this machine is fifty-four lines long. That number hasn't grown much in a long time, and I used to think that meant my Emacs configuration was small. It isn't, really — it's just not in that file.
Run Emacs inside tmux with the stock configuration and you hit the problem within about four seconds. tmux's prefix key is C-b. In Emacs, C-b is backward-char — one of the six or seven keys you press most in any editing session.
Emacs is a serious PHP development environment once you wire the right packages together.
Tree-sitter is a parser generator and incremental parsing library that gives text editors access to a concrete syntax tree of the code being edited. Emacs 29 shipped with built-in tree-sitter support, and Emacs 30 continues to expand it.