Emacs 31.1 will release on 8/24
github.com
August 21, 2026
6 min read
45/100
Summary
GNU Emacs’ HISTORY file records the editor’s evolution from EMACS, a set of macros for the TECO text editor that became operational in late 1976, to the GNU implementation begun in 1984. EMACS drew inspiration from earlier work including Stanford’s E editor and older TECO macro sets. Early GNU Emacs development occurred without version-control systems and was distributed on half-inch, nine-track, 1600-bpi magnetic tape reels; documentation describes surviving details from that period as sketchy. GNU Emacs was rebuilt for GNU and GNU-like systems with a full-featured Lisp at its core. Versions 1.0 through 1.12 were released in early 1985, while version 13 became the initial public release and was announced on Usenet on March 20, 1985. The release record lists stable versions from Emacs 13 through Emacs 31.1, dated August 24, 2026. Recent releases include Emacs 29.1 on July 30, 2023; 29.4 on June 22, 2024; 30.1 on February 23, 2025; and 30.2 on August 14, 2025. Emacs 28.3 is dated February 17, 2023 but marked as not actually released. GNU Emacs is free software under version 3 or later of the GNU General Public License.
Key Takeaways
- EMACS began as TECO editor macros and was first operational in late 1976.
- GNU Emacs development began in 1984 as a new implementation for GNU and GNU-like systems, built around a full-featured Lisp.
- GNU Emacs 13, announced on March 20, 1985, was the initial public release after versions 1.0 through 1.12.
- The release history lists GNU Emacs 31.1 with a date of August 24, 2026.
- GNU Emacs 28.3 is listed with a February 17, 2023 date but is marked as not actually released.
What the discussion said
The thread only lightly engaged with AI, but the people who did saw Emacs as unusually fertile ground for AI-assisted customization. A long-time user described moving away from hand-writing editor extensions: they now ask an AI to reshape windows, shortcuts, and workflow behavior, turning a deeply programmable editor into a personally controlled development environment. Replies argued that this is a particularly good fit because personal configuration code does not need production-grade polish; a rough but functional snippet can still deliver exactly the desired interaction. The practical limitation under discussion was not model intelligence so much as the interface around it. One reader wants AI coding harnesses to preserve a simple interactive terminal mode, where conversations and outputs remain searchable and easy to copy from Emacs buffers. Current embedded terminals and modern AI text interfaces were described as unreliable for nesting Emacs or handling these interactive workflows cleanly. The rest of the thread focused on conventional Emacs release enthusiasm, macOS memory fixes, and future garbage collection work, which did not generate substantive AI-specific debate. Overall, commenters treat AI as a compelling new way to unlock Emacs’s longstanding customizability, while asking for less brittle, more inspectable AI-tool interaction inside the editor.
Community Sentiment
Positives
- AI can turn Emacs customization from a Lisp hobbyist’s task into conversational workflow design, letting users rapidly make the editor behave exactly as they want.
- Messy generated configuration is often good enough: for one-person editor workflows, immediate utility matters more than elegant code or maintainability.
Concerns
- AI coding tools still fit awkwardly into Emacs when their terminal interfaces are hard to search, copy, and recursively run alongside editor-based workflows.
- Fully noninteractive AI harnesses sacrifice the inspectable buffer-oriented interaction that Emacs users rely on for reviewing and reusing model output.