Sed

sed ("stream editor") is a Unix utility that parses and transforms text, using a simple, compact programming language. It was developed from 1973 to 1974 by Lee E. McMahon of Bell Labs, and is available today for most operating systems. sed was based on the scripting features of the interactive editor ed ("editor", 1971) and the earlier qed ("quick editor", 1965–66). It was one of the earliest tools to support regular expressions, and remains in use for text processing, most notably with the substitution command. Popular alternative tools for plaintext string manipulation and "stream editing" include AWK and Perl.

Usage
Always use the -n option to suppress printing all the lines which is a really dumb thing

sed -i 's/{OLD_TERM}/{NEW_TERM}/' {file}

replaces within file not stream

Mode of operation
sed is a line-oriented text processing utility: it reads text, line by line, from an input stream or file, into an internal buffer called the pattern space. Each line read starts a cycle. To the pattern space, sed applies one or more operations which have been specified via a sed script. sed implements a programming language with about 25 commands that specify the operations on the text. For each input line, after running the script, sed ordinarily outputs the pattern space (the line as modified by the script) and begins the cycle again with the next line. Other end-of-script behaviors are available through sed options and script commands, e.g.  to delete the pattern space,   to quit,   to add the next line to the pattern space immediately, and so on. Thus a sed script corresponds to the body of a loop that iterates through the lines of a stream, where the loop itself and the loop variable (the current line number) are implicit and maintained by sed.

The sed script can either be specified on the command line ( option) or read from a separate file (  option). Commands in the sed script may take an optional address, in terms of line numbers or regular expressions. The address determines when the command is run. For example,  would only run the   (delete) command on the second input line (printing all lines but the second), while   would delete all lines beginning with a space. A separate special buffer, the hold space, may be used by a few sed commands to hold and accumulate text between cycles. sed's command language has only two variables (the "hold space" and the "pattern space") and GOTO-like branching functionality; nevertheless, the language is Turing-complete, and esoteric sed scripts exist for games such as sokoban, arkanoid, chess, and tetris.

A main loop executes for each line of the input stream, evaluating the sed script on each line of the input. Lines of a sed script are each a pattern-action pair, indicating what pattern to match and which action to perform, which can be recast as a conditional statement. Because the main loop, working variables (pattern space and hold space), input and output streams, and default actions (copy line to pattern space, print pattern space) are implicit, it is possible to write terse one-liner programs. For example, the sed program given by: 10q will print the first 10 lines of input, then stop.

Substitution command
The following example shows a typical, and the most common, use of sed: substitution. This usage was indeed the original motivation for sed: In some versions of sed, the expression must be preceded by  to indicate that an expression follows. The  stands for substitute, while the   stands for global, which means that all matching occurrences in the line would be replaced. The regular expression (i.e. pattern) to be searched is placed after the first delimiting symbol (slash here) and the replacement follows the second symbol. Slash is the conventional symbol, originating in the character for "search" in ed, but any other could be used to make syntax more readable if it does not occur in the pattern or replacement; this is useful to avoid "leaning toothpick syndrome".

The substitution command, which originates in search-and-replace in ed, implements simple parsing and templating. The  provides both pattern matching and saving text via sub-expressions, while the   can be either literal text, or a format string containing the characters   for "entire match" or the special escape sequences   through   for the nth saved sub-expression. For example,  replaces all occurrences of "cat" or "dog" with "cats" or "dogs", without duplicating an existing "s":   is the 1st (and only) saved sub-expression in the regexp, and   in the format string substitutes this into the output.

Other sed commands
Besides substitution, other forms of simple processing are possible, using some 25 sed commands. For example, the following uses the d command to filter out lines that only contain spaces, or only contain the end of line character: This example uses some of the following regular expression metacharacters (sed supports the full range of regular expressions):
 * The caret matches the beginning of the line.
 * The dollar sign matches the end of the line.
 * The asterisk matches zero or more occurrences of the previous character.
 * The plus matches one or more occurrence(s) of the previous character.
 * The question mark matches zero or one occurrence of the previous character.
 * The dot matches exactly one character.

Complex sed constructs are possible, allowing it to serve as a simple, but highly specialized, programming language. Flow of control, for example, can be managed by the use of a label (a colon followed by a string) and the branch instruction. An instruction  followed by a valid label name will move processing to the block following that label.

sed used as a filter
Under Unix, sed is often used as a filter in a pipeline: That is, a program such as "generateData" generates data, and then sed makes the small change of replacing x with y. For example:

File-based sed scripts
It is often useful to put several sed commands, one command per line, into a script file such as, and then use the   option to run the commands (such as  ) from the file: Any number of commands may be placed into the script file, and using a script file also avoids problems with shell escaping or substitutions.

Such a script file may be made directly executable from the command line by prepending it with a "shebang line" containing the sed command and assigning the executable permission to the file. For example, a file  can be created with contents:

The file may then be made executable by the current user with the  command: The file may then be executed directly from the command line:

In-place editing
The  option, introduced in GNU sed, allows in-place editing of files (actually, a temporary output file is created in the background, and then the original file is replaced by the temporary file). For example:

Hello, world! example
This "Hello, world!" script is in a file (e.g., script.txt) and invoked with, where "inputFileName" is the input text file. The script changes "inputFileName" line #1 to "Hello, world!" and then quits, printing the result before sed exits. Any input lines past line #1 are not read, and not printed. So the sole output is "Hello, world!".

The example emphasizes many key characteristics of sed:
 * Typical sed programs are rather short and simple.
 * sed scripts can have comments (the line starting with the  symbol).
 * The  (substitute) command is the most important sed command.
 * sed allows simple programming, with commands such as  (quit).
 * sed uses regular expressions, such as  (zero or more of any character).

Other simple examples
Below follow various sed scripts; these can be executed by passing as an argument to sed, or put in a separate file and executed via  or by making the script itself executable.

To replace any instance of a certain word in a file with "REDACTED", such as an IRC password, and save the result:

To delete any line containing the word "yourword" (the address is '/yourword/'): To delete all instances of the word "yourword": To delete two words from a file simultaneously: To express the previous example on one line, such as when entering at the command line, one may join two commands via the semicolon:

Multiline processing example
In the next example, sed, which usually only works on one line, removes newlines from sentences where the second line starts with one space. Consider the following text: This is my dog, whose name is Frank. This is my fish, whose name is George. This is my goat, whose name is Adam.

The sed script below will turn the text above into the following text. Note that the script affects only the input lines that start with a space: This is my dog, whose name is Frank. This is my fish, whose name is George. This is my goat, whose name is Adam.

The script is: This is explained as:
 * add the next line to the pattern space;
 * find a new line followed by a space, replace with one space;
 * print the top line of the pattern space;
 * delete the top line from the pattern space and run the script again.

This can be expressed on a single line via semicolons: sed 'N; s/\n / /; P; D' inputFileName

Limitations and alternatives
While simple and limited, sed is sufficiently powerful for a large number of purposes. For more sophisticated processing, more powerful languages such as AWK or Perl are used instead. These are particularly used if transforming a line in a way more complicated than a regex extracting and template replacement, though arbitrarily complicated transforms are in principle possible by using the hold buffer.

Conversely, for simpler operations, specialized Unix utilities such as grep (print lines matching a pattern), head (print the first part of a file), tail (print the last part of a file), and tr (translate or delete characters) are often preferable. For the specific tasks they are designed to carry out, such specialized utilities are usually simpler, clearer, and faster than a more general solution such as sed.

The ed/sed commands and syntax continue to be used in descendent programs, such as the text editors vi and vim. An analog to ed/sed is sam/ssam, where sam is the Plan 9 editor, and ssam is a stream interface to it, yielding functionality similar to sed.

Tutorials

 * Sed - An Introduction and Tutorial, by Bruce Barnett
 * SED -- A Non-interactive Text Editor (1974), by Lee E. McMahon
 * 31+ Examples For Sed Linux Command In Text Manipulation, by Mokhtar Ebrahim

Examples

 * Major sources for sed scripts, files, usage
 * Roger Chang's SED and Shell Scripts (2012)
 * Top 'sed' commands – Usage examples
 * Sed command examples in Unix & Linux

Other links

 * (includes manual)