| Revision as of 20:52, 7 September 2002 editHirzel (talk | contribs)1,146 edits Added metacharacters← Previous edit | Revision as of 20:53, 7 September 2002 edit undoHirzel (talk | contribs)1,146 editsmNo edit summaryNext edit → | ||
| Line 20: | Line 20: | ||
| This example used some of the following metacharacters: | This example used some of the following metacharacters: | ||
| ^ Matches the beginning of the line | - ^ Matches the beginning of the line | ||
| $ Matches the end of the line | - $ Matches the end of the line | ||
| . Matches any single character | - . Matches any single character | ||
| * Will match zero or more occurrences of the previous character | - * Will match zero or more occurrences of the previous character | ||
| Matches all the characters inside the | - Matches all the characters inside the | ||
| Sed is one of the very early unix commands that permitted command line processing of data files. Cousin to the later ], 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. | Sed is one of the very early unix commands that permitted command line processing of data files. Cousin to the later ], 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. | ||
Revision as of 20:53, 7 September 2002
Sed (which stands for Stream EDitor) is a originally a UNIX utility but is available for any operating system which supports a command line. It allows to modify text files. It reads input files line by line, transforms these lines according to rules specified in a certain simple language, and outputs them. The rules often involve regular expressions.
The following example shows a typical usage of sed:
sed -e 's/OldExpression1/NewExpression/g' aFileName
Under Unix this can be combined with a pipe
- generate_data | sed -e 's/x/y/'
That is, generate the data, but make the small change of replacing x by y.
The s stands for substitute, the g stands for global. That means in the whole line. After the first slash there is the expression to search for and after the second slash there is the expression to substitute instead. The first expression can be a regular expression.
Several substitutions can be put togehter 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 is possible. For example the following script deletes empty lines or lines which only contain spaces.
sed -e '/^ *$/d' inputFileName
This example used some of the following metacharacters: - ^ Matches the beginning of the line - $ Matches the end of the line - . Matches any single character - * Will match zero or more occurrences of the previous character - Matches all the characters inside the
Sed is one of the very early unix commands that permitted command line processing of data files. 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.
If you have to do several substitutions you can put them in a file and use the following command:
sed -f subst.sed inputfileName > outputfileName
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 only primitive GOTO and branching functionality; nevertheless, the language is Turing complete.
Weblinks: