Sed

Template:For Template:Title sed (which stands for Stream EDitor) is a simple but powerful computer program used to apply various pre-specified textual transformations to a sequential stream of text data. It reads input files line by line, edits each line according to rules specified in its simple language (the sed script), and then outputs the line. While originally created as a UNIX utility by Lee E. McMahon of Bell Labs in 1973/1974, sed is now available for virtually every operating system that supports a command line.

sed is often thought of as a non-interactive text editor. It differs from conventional text editors in that the processing of the two inputs is inverted. Instead of iterating once through a list of edit commands applying each one to the whole text file in memory, sed iterates once through the text file applying the whole list of edit commands to each line. Because only one line at a time is in memory, sed can process arbitrarily-large text files.

sed's command set is modeled after the ed editor, and most commands work similarly in this inverted paradigm. For example, the command 25d means if this is line 25, then delete (don't output) it, rather than go to line 25 and delete it as it does in ed. The notable exception is the copy and move commands, which span a range of lines and thus don't have straight-forward equivalents in sed. Instead, sed introduces an extra buffer called the hold space, and additional commands to manipulate it. The ed command to copy line 25 to line 76 (25t76) for example would be coded as two separate commands in sed (25h; 76g), to store the line in the hold space until the point at which it should be retrieved.

The following example shows a typical usage of sed:

   sed -e 's/oldstuff/newstuff/g' inputFileName > outputFileName

The s stands for substitute; the g stands for global. That means in the whole line. After the first slash is the regular expression to search for and after the second slash is the expression to replace it with. The substitute command (s///) is by far the most powerful and most commonly used sed command.

Under Unix, sed is often used as a filter in a pipeline:

   generate_data | sed -e 's/x/y/'

That is, generate the data, but make the small change of replacing x with y.

Several substitutions or other commands can be put together in a file called, for example, subst.sed and then be applied like

   sed -f subst.sed inputFileName > outputFileName

Besides substitution, other forms of simple processing are possible. For example, the following script deletes empty lines or lines that only contain spaces:

   sed -e '/^ *$/d' inputFileName 

This example used some of the following regular expression metacharacters:

• ^ Matches the beginning of the line
• $ Matches the end of the line
• . Matches any single character
• * Matches zero or more occurrences of the previous character
• [ ] Matches any of the characters inside the [ ]

Complex sed constructs are however possible, to the extent that it can be conceived of as a highly specialised, albeit simple, programming language. Flow of control, for example, can be managed by use of a label (a colon followed by a string which is to be the label name) and the branch instruction b; an instruction b followed by a valid label name will move processing to the block following the label; if the label does not exist then the branch will end the script.

sed is one of the very early Unix commands that permitted command line processing of data files. It evolved as the natural successor to the popular grep command. Cousin to the later AWK, sed allowed powerful and interesting data processing to be done by shell scripts. Sed was probably the earliest Unix tool that really encouraged regular expressions to be used ubiquitously. In terms of speed of operation, sed is generally faster than perl in execution and markedly faster than AWK.

sed and AWK are often cited as the progenitors and inspiration for Perl; in particular the s/// syntax from the example above is part of Perl's syntax.

sed's language does not have variables and has only primitive GOTO and branching functionality; nevertheless, the language is Turing-complete.

GNU sed includes several new features such as in-place editing of files (i.e., replace the original file with the result of applying the sed program). In-place editing is often used instead of ed scripts: for example,

   sed -i 's/abc/def/' file

can be used instead of

   ed file
   1,$ s/abc/def/
   w
   q

There is an extended version of sed called Super-sed (ssed) that includes regular expressions compatible with Perl.

External links

• A very basic introduction (http://www.cs.hmc.edu/qref/sed.html)
• Major sources for sed scripts, files, usage (http://sed.sourceforge.net)
• The sed FAQ (http://sed.sourceforge.net/sedfaq.html)
• Handy one-line sed scripts (http://sed.sourceforge.net/sed1line.txt)
• A home page for sed, some focus on Windows/DOS (http://www.pement.org/sed/)
• Paper describing Turing machine in sed, and its universality (http://sed.sourceforge.net/grabbag/scripts/turing.txt)
• Turing machine in sed, the actual script (http://sed.sourceforge.net/grabbag/scripts/turing.sed)
• Super-sed (http://www.gnu.org/directory/text/editors/super-sed.html)
• sed Sokoban (http://aurelio.net/sed/sokoban/)
• sed . . . the stream editor resources webpage (http://www.student.northpark.edu/pemente/sed/)ca:Sed

de:sed fr:sed ja:sed nl:sed pl:sed (program) pt:Sed ru:Sed