A text editor is the program a programmer spends more time inside than any other: the tool that accepts keystrokes and turns them into a file of characters. Unlike a word processor, an editor for code cares about exact bytes, not page layout. The history of programming is in large part the history of making this one tool faster, more expressive, and more under the user’s control.
The earliest editors were line editors, built for teletypes and printing terminals that could not move a cursor freely around a screen. The Version 7 Unix manual page calls ed simply “the standard text editor.” With ed the user addresses lines by number or by pattern, prints them, and substitutes within them, never seeing the whole file at once. This style was a direct response to the hardware: when output is printed on paper one line at a time, an editor that thinks in lines is the natural fit. Line editors such as ed, and DEC’s TECO, defined the first generation.
When video terminals made it cheap to repaint a screen, the screen editor arrived. Now the file could be shown as a window of text with a cursor moving in two dimensions, and editing commands operated on what the user could see. Screen editors such as vi and the display version of Emacs replaced the print-and-address loop with direct manipulation, and they remain the dominant model. The shift from line to screen was a shift in mental model as much as in technology: editing became something you watched happen.
The third leap was extensibility. In his EMACS paper, Richard Stallman describes a “real-time display editor which can be extended by the user while it is running,” arguing that the editor’s command set should not be fixed by its authors but grown by its users. An extensible editor exposes a programming language so that any behavior, from a new keybinding to a whole new mode, can be added without recompiling. This idea, born in TECO macros and matured in Emacs Lisp, turned the editor from an appliance into a platform.
These three generations did not fully replace each other. Line editors still live inside scripts and as the underlying model of stream tools; screen editing is the default everywhere; extensibility now defines the line between a plain editor and an integrated development environment. The modern editor blends all three: a screen-oriented surface, a scripting layer, and features such as syntax highlighting and language servers layered on top. The text editor endures as the programmer’s primary instrument because it sits exactly where human intent meets machine-readable text.