SED(1)\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 User Commands\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 SED(1)<\/p>\n
NAME<\/p>\n
sed – stream editor for filtering and transforming text<\/p>\n
SYNOPSIS<\/p>\n
sed [OPTION]… {script-only-if-no-other-script} [input-file]…<\/p>\n
DESCRIPTION<\/p>\n
Sed is a stream editor.\u00a0 A stream editor is used to perform basic
\ntext transformations on an input stream (a file or input from a
\npipeline).\u00a0 While in some ways similar to an editor which permits
\nscripted edits (such as ed), sed works by making only one pass over
\nthe input(s), and is consequently more efficient.\u00a0 But it is sed’s
\nability to filter text in a pipeline which particularly distinguishes
\nit from other types of editors.<\/p>\n
-n, –quiet, –silent<\/p>\n
suppress automatic printing of pattern space<\/p>\n
-e script, –expression=script<\/p>\n
add the script to the commands to be executed<\/p>\n
-f script-file, –file=script-file<\/p>\n
add the contents of script-file to the commands to be executed<\/p>\n
–follow-symlinks<\/p>\n
follow symlinks when processing in place<\/p>\n
-i[SUFFIX], –in-place[=SUFFIX]<\/p>\n
edit files in place (makes backup if SUFFIX supplied)<\/p>\n
-l N, –line-length=N<\/p>\n
specify the desired line-wrap length for the `l’ command<\/p>\n
–posix<\/p>\n
disable all GNU extensions.<\/p>\n
-r, –regexp-extended<\/p>\n
use extended regular expressions in the script.<\/p>\n
-s, –separate<\/p>\n
consider files as separate rather than as a single continuous
\nlong stream.<\/p>\n
-u, –unbuffered<\/p>\n
load minimal amounts of data from the input files and flush
\nthe output buffers more often<\/p>\n
-z, –null-data<\/p>\n
separate lines by NUL characters<\/p>\n
–help
\ndisplay this help and exit<\/p>\n
–version
\noutput version information and exit<\/p>\n
If no -e, –expression, -f, or –file option is given, then the first
\nnon-option argument is taken as the sed script to interpret.\u00a0 All
\nremaining arguments are names of input files; if no input files are
\nspecified, then the standard input is read.<\/p>\n
GNU sed home page: <http:\/\/www.gnu.org\/software\/sed\/>.\u00a0 General help
\nusing GNU software: <http:\/\/www.gnu.org\/gethelp\/>.\u00a0 E-mail bug
\nreports to: <bug-sed@gnu.org>.\u00a0 Be sure to include the word “sed”
\nsomewhere in the “Subject:” field.<\/p>\n
COMMAND SYNOPSIS<\/p>\n
This is just a brief synopsis of sed commands to serve as a reminder
\nto those who already know sed; other documentation (such as the
\ntexinfo document) must be consulted for fuller descriptions.<\/p>\n
Zero-address “commands”
\n: label
\nLabel for b and t commands.<\/p>\n
#comment
\nThe comment extends until the next newline (or the end of a -e
\nscript fragment).<\/p>\n
}\u00a0\u00a0\u00a0\u00a0\u00a0 The closing bracket of a { } block.<\/p>\n
Zero- or One- address commands
\n=\u00a0\u00a0\u00a0\u00a0\u00a0 Print the current line number.<\/p>\n
a \\<\/p>\n
text\u00a0\u00a0 Append text, which has each embedded newline preceded by a
\nbackslash.<\/p>\n
i \\<\/p>\n
text\u00a0\u00a0 Insert text, which has each embedded newline preceded by a
\nbackslash.<\/p>\n
q [exit-code]
\nImmediately quit the sed script without processing any more
\ninput, except that if auto-print is not disabled the current
\npattern space will be printed.\u00a0 The exit code argument is a
\nGNU extension.<\/p>\n
Q [exit-code]
\nImmediately quit the sed script without processing any more
\ninput.\u00a0 This is a GNU extension.<\/p>\n
r filename
\nAppend text read from filename.<\/p>\n
R filename
\nAppend a line read from filename.\u00a0 Each invocation of the
\ncommand reads a line from the file.\u00a0 This is a GNU extension.<\/p>\n
Commands which accept address ranges
\n{\u00a0\u00a0\u00a0\u00a0\u00a0 Begin a block of commands (end with a }).<\/p>\n
b label
\nBranch to label; if label is omitted, branch to end of script.<\/p>\n
c \\<\/p>\n
text\u00a0\u00a0 Replace the selected lines with text, which has each embedded
\nnewline preceded by a backslash.<\/p>\n
d\u00a0\u00a0\u00a0\u00a0\u00a0 Delete pattern space.\u00a0 Start next cycle.<\/p>\n
D\u00a0\u00a0\u00a0\u00a0\u00a0 If pattern space contains no newline, start a normal new cycle
\nas if the d command was issued.\u00a0 Otherwise, delete text in the
\npattern space up to the first newline, and restart cycle with
\nthe resultant pattern space, without reading a new line of
\ninput.<\/p>\n
h H\u00a0\u00a0\u00a0 Copy\/append pattern space to hold space.<\/p>\n
g G\u00a0\u00a0\u00a0 Copy\/append hold space to pattern space.<\/p>\n
l\u00a0\u00a0\u00a0\u00a0\u00a0 List out the current line in a “visually unambiguous” form.<\/p>\n
l width
\nList out the current line in a “visually unambiguous” form,
\nbreaking it at width characters.\u00a0 This is a GNU extension.<\/p>\n
n N\u00a0\u00a0\u00a0 Read\/append the next line of input into the pattern space.<\/p>\n
p\u00a0\u00a0\u00a0\u00a0\u00a0 Print the current pattern space.<\/p>\n
P\u00a0\u00a0\u00a0\u00a0\u00a0 Print up to the first embedded newline of the current pattern
\nspace.<\/p>\n
s\/regexp\/replacement\/
\nAttempt to match regexp against the pattern space.\u00a0 If
\nsuccessful, replace that portion matched with replacement.
\nThe replacement may contain the special character & to refer
\nto that portion of the pattern space which matched, and the
\nspecial escapes \\1 through \\9 to refer to the corresponding
\nmatching sub-expressions in the regexp.<\/p>\n
t label
\nIf a s\/\/\/ has done a successful substitution since the last
\ninput line was read and since the last t or T command, then
\nbranch to label; if label is omitted, branch to end of script.<\/p>\n
T label
\nIf no s\/\/\/ has done a successful substitution since the last
\ninput line was read and since the last t or T command, then
\nbranch to label; if label is omitted, branch to end of script.
\nThis is a GNU extension.<\/p>\n
w filename
\nWrite the current pattern space to filename.<\/p>\n
W filename
\nWrite the first line of the current pattern space to filename.
\nThis is a GNU extension.<\/p>\n
x\u00a0\u00a0\u00a0\u00a0\u00a0 Exchange the contents of the hold and pattern spaces.<\/p>\n
y\/source\/dest\/
\nTransliterate the characters in the pattern space which appear
\nin source to the corresponding character in dest.<\/p>\n
Addresses
\nSed commands can be given with no addresses, in which case the
\ncommand will be executed for all input lines; with one address, in
\nwhich case the command will only be executed for input lines which
\nmatch that address; or with two addresses, in which case the command
\nwill be executed for all input lines which match the inclusive range
\nof lines starting from the first address and continuing to the second
\naddress.\u00a0 Three things to note about address ranges: the syntax is
\naddr1,addr2 (i.e., the addresses are separated by a comma); the line
\nwhich addr1 matched will always be accepted, even if addr2 selects an
\nearlier line; and if addr2 is a regexp, it will not be tested against
\nthe line that addr1 matched.<\/p>\n
After the address (or address-range), and before the command, a !
\nmay be inserted, which specifies that the command shall only be
\nexecuted if the address (or address-range) does not match.<\/p>\n
The following address types are supported:<\/p>\n
number Match only the specified line number (which increments
\ncumulatively across files, unless the -s option is specified
\non the command line).<\/p>\n
first~step
\nMatch every step’th line starting with line first.\u00a0 For
\nexample, “sed -n 1~2p” will print all the odd-numbered lines
\nin the input stream, and the address 2~5 will match every
\nfifth line, starting with the second.\u00a0 first can be zero; in
\nthis case, sed operates as if it were equal to step.\u00a0 (This is
\nan extension.)<\/p>\n
$\u00a0\u00a0\u00a0\u00a0\u00a0 Match the last line.<\/p>\n
\/regexp\/
\nMatch lines matching the regular expression regexp.<\/p>\n
\\cregexpc
\nMatch lines matching the regular expression regexp.\u00a0 The c may
\nbe any character.<\/p>\n
GNU sed also supports some special 2-address forms:<\/p>\n
0,addr2
\nStart out in “matched first address” state, until addr2 is
\nfound.\u00a0 This is similar to 1,addr2, except that if addr2
\nmatches the very first line of input the 0,addr2 form will be
\nat the end of its range, whereas the 1,addr2 form will still
\nbe at the beginning of its range.\u00a0 This works only when addr2
\nis a regular expression.<\/p>\n
addr1,+N
\nWill match addr1 and the N lines following addr1.<\/p>\n
addr1,~N
\nWill match addr1 and the lines following addr1 until the next
\nline whose input line number is a multiple of N.<\/p>\n
REGULAR EXPRESSIONS<\/p>\n
POSIX.2 BREs should be supported, but they aren’t completely because
\nof performance problems.\u00a0 The \\n sequence in a regular expression
\nmatches the newline character, and similarly for \\a, \\t, and other
\nsequences.<\/p>\n
BUGS<\/p>\n
E-mail bug reports to\u00a0bug-sed@gnu.org.\u00a0 Also, please include the
\noutput of “sed –version” in the body of your report if at all
\npossible.<\/p>\n
AUTHOR<\/p>\n
Written by Jay Fenlason, Tom Lord, Ken Pizzini, and Paolo Bonzini.
\nGNU sed home page: <http:\/\/www.gnu.org\/software\/sed\/>.\u00a0 General help
\nusing GNU software: <http:\/\/www.gnu.org\/gethelp\/>.\u00a0 E-mail bug
\nreports to: <bug-sed@gnu.org>.\u00a0 Be sure to include the word “sed”
\nsomewhere in the “Subject:” field.<\/p>\n
COPYRIGHT<\/p>\n
Copyright \u00a9 2012 Free Software Foundation, Inc.\u00a0 License GPLv3+: GNU
\nGPL version 3 or later <http:\/\/gnu.org\/licenses\/gpl.html>.
\nThis is free software: you are free to change and redistribute it.
\nThere is NO WARRANTY, to the extent permitted by law.<\/p>\n
SEE ALSO<\/p>\n
awk(1), ed(1), grep(1), tr(1), perlre(1), sed.info, any of various
\nbooks on sed, the sed FAQ
\n(http:\/\/sed.sf.net\/grabbag\/tutorials\/sedfaq.txt),
\nhttp:\/\/sed.sf.net\/grabbag\/.<\/p>\n
The full documentation for sed is maintained as a Texinfo manual.\u00a0 If
\nthe info and sed programs are properly installed at your site, the
\ncommand<\/p>\n
info sed<\/p>\n
should give you access to the complete manual.<\/p>\n
COLOPHON<\/p>\n
This page is part of the sed (stream-oriented editor) project.
\nInformation about the project can be found at
\n\u27e8http:\/\/www.gnu.org\/software\/sed\/\u27e9.\u00a0 If you have a bug report for this
\nmanual page, send it to\u00a0bug-sed@gnu.org.\u00a0 This page was obtained from
\nthe tarball sed-4.2.2.tar.gz fetched from
\n\u27e8https:\/\/www.gnu.org\/software\/sed\/\u27e9 on 2014-12-30.\u00a0 If you discover
\nany rendering problems in this HTML version of the page, or you
\nbelieve there is a better or more up-to-date source for the page, or
\nyou have corrections or improvements to the information in this
\nCOLOPHON (which is not part of the original manual page), send a mail
\nto\u00a0man-pages@man7.org<\/p>\n
sed 4.2.2\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 December 2012\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 SED(1)<\/p>\n","protected":false},"excerpt":{"rendered":"
SED(1)\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 User Commands\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 SED(1) NAME sed – stream editor for filtering and transforming text SYNOPSIS sed [OPTION]… {script-only-if-no-other-script} [input-file]… DESCRIPTION Sed is a stream editor.\u00a0 A stream editor is used to perform basic text transformations on an input stream (a file or input from a pipeline).\u00a0 While in some ways similar to an editor which […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_sitemap_exclude":false,"_sitemap_priority":"","_sitemap_frequency":"","footnotes":""},"categories":[8],"tags":[],"class_list":["post-345","post","type-post","status-publish","format-standard","hentry","category-shell"],"a3_pvc":{"activated":false,"total_views":0,"today_views":0},"_links":{"self":[{"href":"https:\/\/www.linuxboxen.dk\/index.php?rest_route=\/wp\/v2\/posts\/345","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.linuxboxen.dk\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.linuxboxen.dk\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.linuxboxen.dk\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.linuxboxen.dk\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=345"}],"version-history":[{"count":0,"href":"https:\/\/www.linuxboxen.dk\/index.php?rest_route=\/wp\/v2\/posts\/345\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.linuxboxen.dk\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=345"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.linuxboxen.dk\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=345"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.linuxboxen.dk\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=345"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}