emacs-mirror/emacs
Productivity & UtilitiesGNU Emacs is a self-documenting, extensible text editor whose Emacs Lisp layer lets users build and customize their own editing environment.
What This Is
This repository is a mirror of GNU Emacs, the Free Software Foundation's extensible, self-documenting, real-time display editor (currently version 32.0.50 in development). It is not just a text editor: the C core implements the Emacs Lisp interpreter, redisplay, and basic editing primitives, while the lisp directory holds most of the user-facing functionality — editing modes, the minibuffer, dired, mail, and so on. The src and lisp split is the key architectural fact: almost everything a user sees is written in Emacs Lisp and can be inspected and redefined at runtime.
The tree also contains the source for the Emacs Manual, the Emacs Lisp reference manual, tests, Android and MS-Windows port files, and separate platform README files. People who want to develop Emacs itself should read CONTRIBUTE and etc/NEWS for recent changes.
Build and Install
Building from this tree requires a C toolchain and the usual GNU build tools; on non-POSIX platforms additional tools are needed and listed in the platform-specific READMEs. The documented flow is the standard Autoconf one:
- Ensure the build dependencies for your platform are installed (see
INSTALL). - From the top of the unpacked tree, run the
configureshell script to generate aMakefiletuned to your processor and OS. - Run
maketo build, and install perINSTALL. - If you are working on
configure.acor modifying the autobuild procedure, runautogen.shfirst, which requires recent Autoconf and GNU m4.
The README does not spell out every configure flag or an exact make install invocation; those details are in INSTALL and etc/PROBLEMS at the top of the tree. Prebuilt binaries are available from the official GNU Emacs site rather than from this mirror.
Everyday Use
Anything typed is a command invocation or text insertion; Emacs Lisp can be evaluated interactively to change behavior on the spot. The info directory ships the Info documentation tree, and etc contains the tutorial text and other architecture-independent data files. The README explicitly notes that it concerns documentation and building, not feature descriptions — new user-visible changes go in etc/NEWS.
Constraints
- License: GPL-3.0-or-later; redistribution and modification carry the usual copyleft obligations.
- Building on non-POSIX platforms (MS-DOS, MS-Windows, Android, GNUstep/macOS Cocoa) requires tools outside the standard OS distribution, and each port has its own instructions.
- Regenerating the manuals requires
makeinfofrom GNU Texinfo at a sufficiently recent version. - Bug reports go to
bug-gnu-emacs@gnu.orgor viaM-x report-emacs-bug; the README warns bugs are likely in this development version.
Community Reports
An HN thread about the planned Emacs 31.1 release (August 21, 2026) drew long-time users describing its role as a personal, fully controllable text environment. One commenter with 32 years of use described asking AI to write small Emacs functions for customized window and key behavior jwr, 2026-08-21; another observed that Emacs Lisp configuration is forgiving enough that AI-generated code working despite being messy is fine LiamPowell, 2026-08-21. A separate comment links the feature/igc3 branch as a possible new GC in Emacs 32 BoingBoomTschak, 2026-08-21. These are user opinions about workflow, not statements of project policy.
HotRepo's Take
There is no GitHub daily ranking or star-growth snapshot for this mirror, so the station's data says nothing about its popularity — which is unsurprising for a years-old mirror of a canonical GNU project. The more useful signal in the supplied records is the discussion: the August 2026 release thread was active, and commenters framed Emacs not as a declining editor but as the substrate for custom tooling, including AI-assisted configuration. For readers, the practical takeaway is that the value here is the source tree and its documentation (README, INSTALL, etc/NEWS, manuals), not any packaged download, and that development happens upstream with the FSF mailing lists and Savannah as the coordination points.
Written by AI from the project's README, updated . The project's own docs are the source of truth.