Story
What's new in Emacs 31.1
1 report
1 website
1 discussion
Latest report
Overview
Emacs 31.1 has been released with incremental usability, completion, window-management and terminal improvements rather than a single flagship feature. The release permanently removes the legacy unexec dumper, deprecated since Emacs 27, leaving the portable dumper as the supported mechanism for preloading Emacs Lisp state. It also stops building and installing Emacs’s old ctags program, directing users to Universal Ctags or to `etags --ctags` for compatible behavior. A planned new garbage collector was postponed to Emacs 32. A new User Lisp Directory feature automatically processes Lisp files under `user-lisp/` in an Emacs configuration directory, including recursive byte compilation, autoload generation and load-path setup. Tree-sitter modes can now offer to install their required language grammars. Completion gains configurable eager display and live updating of the *Completions* buffer, while the rewritten flex completion style is intended to be faster and rank matches more accurately. New commands rotate, flip and transpose window layouts, and a setting controls preferred split direction. Compatible terminals now enable `xterm-mouse-mode` by default, and TTY frames gain child-frame support. Emacs 31.1 also adds built-in controls for collapsing minor-mode indicators, hiding a buffer’s mode line, extending selections with Shift-click, and preventing asynchronous native compilation on battery power. It includes Org 9.8 and supports Unicode Standard 17.0.
Summary from masteringemacs.org.
Reports
One report so far. Additional coverage will appear here when it is linked to this story.
masteringemacs.org
What's new in Emacs 31.1
Read report →
Community reactions
Each reaction summarizes sampled comments from the linked discussion.
Hacker News · masteringemacs.org
Historical count: 7 · 7 saved in sample · Historical sample
Analysis ready
Read this discussion’s reaction
Based on 7 sampled comments from this thread. Analyzed 2026-08-25.
The thread barely engages with AI at all. Most of the discussion is about Emacs Lisp learning resources, built-in editor features, package-management details, and Tree-sitter installation problems; those are outside the AI/ML scope. The lone AI-adjacent moment comes when one reader, considering a move back from Zed to Emacs, is asked whether Zed’s AI features would be a meaningful loss. No answer follows, so the conversation supplies neither a verdict on AI-assisted editing nor evidence about feature quality, model capability, cost, privacy, or workflow impact. That absence is itself the clearest takeaway: commenters evaluating Emacs 31.1 were focused on making a leaner, more built-in configuration and on reducing friction around language tooling, not on replacing or adopting AI coding assistants. There is no visible enthusiasm for AI features, but also no criticism of them; the topic simply fails to become part of the release discussion. The thread therefore offers no defensible model, product, safety, or developer-experience conclusion about AI beyond one unresolved prompt about whether an alternative editor’s AI tooling is worth missing.