|Original author(s)||Ken Thompson|
|Developer(s)||AT&T Bell Laboratories|
|Initial release||1973, 49–50 years ago|
|Operating system||Unix, Unix-like, Plan 9|
|License||Plan 9: MIT License|
ed (pronounced as distinct letters, //) is a line editor for Unix and Unix-like operating systems. It was one of the first parts of the Unix operating system that was developed, in August 1969. It remains part of the POSIX and Open Group standards for Unix-based operating systems, alongside the more sophisticated full-screen editor vi.
History and influence
The ed text editor was one of the first three key elements of the Unix operating system—assembler, editor, and shell—developed by Ken Thompson in August 1969 on a PDP-7 at AT&T Bell Labs. Many features of ed came from the qed text editor developed at Thompson's alma mater University of California, Berkeley. Thompson was very familiar with qed, and had reimplemented it on the CTSS and Multics systems. Thompson's versions of qed were notable as the first to implement regular expressions. Regular expressions are also implemented in ed, though their implementation is considerably less general than that in qed.
Dennis M. Ritchie produced what Doug McIlroy later described as the "definitive" ed, and aspects of ed went on to influence ex, which in turn spawned vi. The non-interactive Unix command grep was inspired by a common special use of qed and later ed, where the command
g/re/p performs a global regular expression search and prints the lines containing matches. The Unix stream editor, sed implemented many of the scripting features of qed that were not supported by ed on Unix.[failed verification]
Features of ed include:
- available on essentially all Unix systems (and mandatory on systems conforming to the Single Unix Specification).
- support for regular expressions
- powerful automation can be achieved by feeding commands from standard input
(In)famous for its terseness, ed, compatible with teletype terminals like Teletype Model 33, gives almost no visual feedback, and has been called (by Peter H. Salus) "the most user-hostile editor ever created", even when compared to the contemporary (and notoriously complex) TECO. For example, the message that ed will produce in case of error, and when it wants to make sure the user wishes to quit without saving, is "?". It does not report the current filename or line number, or even display the results of a change to the text, unless requested. Older versions (c. 1981) did not even ask for confirmation when a quit command was issued without the user saving changes. This terseness was appropriate in the early versions of Unix, when consoles were teletypes, modems were slow, and memory was precious. As computer technology improved and these constraints were loosened, editors with more visual feedback became the norm.
In current practice, ed is rarely used interactively, but does find use in some shell scripts. For interactive use, ed was subsumed by the sam, vi and Emacs editors in the 1980s. ed can be found on virtually every version of Unix and Linux available, and as such is useful for people who have to work with multiple versions of Unix. On Unix-based operating systems, some utilities like SQL*Plus run ed as the editor if the EDITOR and VISUAL environment variables are not defined. If something goes wrong, ed is sometimes the only editor available. This is often the only time when it is used interactively.
The version of ed provided by GNU has a few switches to enhance the feedback. Using
ed -v -p: provides a simple prompt and enables more useful feedback messages. The
-p switch is defined in POSIX since XPG2 (1987).
The ed commands are often imitated in other line-based editors. For example, EDLIN in early MS-DOS versions and 32-bit versions of Windows NT has a somewhat similar syntax, and text editors in many MUDs (LPMud and descendants, for example) use ed-like syntax. These editors, however, are typically more limited in function.
Here is an example transcript of an ed session. For clarity, commands and text typed by the user are in normal face, and output from ed is emphasized.
a ed is the standard Unix text editor. This is line number two. . 2i . ,l ed is the standard Unix text editor.$ $ This is line number two.$ w text 63
3s/two/three/,l ed is the standard Unix text editor.$ $ This is line number three.$ w text 65 q
The end result is a simple text file containing the following text:
ed is the standard Unix text editor. This is line number three.
Started with an empty file, the
a command appends text (all ed commands are single letters). The command puts ed in insert mode, inserting the characters that follow and is terminated by a single dot on a line. The two lines that are entered before the dot end up in the file buffer. The
2i command also goes into insert mode, and will insert the entered text (a single empty line in our case) before line two. All commands may be prefixed by a line number to operate on that line.
In the line
,l, the lowercase L stands for the list command. The command is prefixed by a range, in this case
, which is a shortcut for
1,$. A range is two line numbers separated by a comma (
$ means the last line). In return, ed lists all lines, from first to last. These lines are ended with dollar signs, so that white space at the end of lines is clearly visible.
Once the empty line is inserted in line 2, the line which reads "This is line number two." is now actually the third line. This error is corrected with
3s/two/three/, a substitution command. The
3 will apply it to the correct line; following the command is the text to be replaced, and then the replacement. Listing all lines with
,l the line is shown now to be correct.
w text writes the buffer to the file "text" making ed respond with 65, the number of characters written to the file.
q will end an ed session.
The GNU Project has numerous jokes around ed hosted on its website. In addition, the glibc documentation notes an error code called
ED with its description (errorstr) merely a single question mark, noting "the experienced user will know what is wrong."
- Edlin, the standard MS-DOS line editor which was inspired by ed
- Sam (text editor)
- Editor war
- List of Unix commands
- Computerphile (2018-07-06), Where GREP Came From – Computerphile, archived from the original on 2021-12-11, retrieved 2020-10-21
- Salus, Peter H. (2005). The Daemon, the Gnu and the Penguin. Groklaw. Archived from the original on 2010-05-05.
- The Single UNIX Specification, Version 4 from The Open Group – Shell and Utilities Reference,
- D. M. Ritchie and K. L. Thompson, "QED Text Editor", MM-70-1373-3 (June 1970), reprinted as "QED Text Editor Reference Manual", MHCC-004, Murray Hill Computing, Bell Laboratories (October 1972).
- McIlroy, M. D. (1987). A Research Unix reader: annotated excerpts from the Programmer's Manual, 1971–1986 (PDF) (Technical report). CSTR. Bell Labs. 139.
- Raymond, Eric (2003). "The Art of Unix Programming" (PDF). Archived (PDF) from the original on June 15, 2023. Retrieved June 14, 2023.
"On the Early History and Impact of Unix".
A while later a demand arose for another special-purpose program, gres, for substitution: g/re/s. Lee McMahon undertook to write it, and soon foresaw that there would be no end to the family: g/re/d, g/re/a, etc. As his concept developed it became sed…
- Donald A. Norman (1981). "The truth about UNIX" (PDF). Datamation. Archived from the original (PDF) on 2014-04-16.
- Administering SQL*Plus. Accessed 7/23/2016.
- Linux General Commands Manual –
- "The GNU C Library - Error Codes". www.gnu.org.
- The Single UNIX Specification, Version 4 from The Open Group : edit text – Shell and Utilities Reference,
- Manual page from Unix First Edition describing ed.
- Version 7 Unix Programmer's Manual : text editor –
- Plan 9 Programmer's Manual, Volume 1, a direct descendant of the original ed. : text editor –
- GNU ed homepage
- A History of UNIX before Berkeley section 3.1 describes the history of ed.