{"id":362,"date":"2011-06-15T15:07:00","date_gmt":"2011-06-16T00:07:00","guid":{"rendered":"\/blog\/?p=362"},"modified":"2023-09-21T09:38:56","modified_gmt":"2023-09-21T00:38:56","slug":"sed-%ec%82%ac%ec%9a%a9%eb%b0%a9%eb%b2%95-%ec%a0%95%eb%a6%ac","status":"publish","type":"post","link":"https:\/\/hasu0707.duckdns.org\/blog\/?p=362","title":{"rendered":"sed \uc0ac\uc6a9\ubc29\ubc95 \uc815\ub9ac"},"content":{"rendered":"\n-------------------------------------------------------------------------<\/span>
\nUSEFUL ONE-LINE SCRIPTS FOR SED (Unix stream editor)        Dec. 29, 2005<\/span>
\nCompiled by Eric Pement - pemente[at]northpark[dot]edu        version 5.5<\/span>
\n
\nLatest version of this file (in English) is usually at:<\/span>
\n   http:\/\/sed.sourceforge.net\/sed1line.txt<\/span>
\n   http:\/\/www.pement.org\/sed\/sed1line.txt<\/span>
\n
\nThis file will also available in other languages:<\/span>
\n  Chinese     - http:\/\/sed.sourceforge.net\/sed1line_zh-CN.html<\/span>
\n  Czech       - http:\/\/sed.sourceforge.net\/sed1line_cz.html<\/span>
\n  Dutch       - http:\/\/sed.sourceforge.net\/sed1line_nl.html<\/span>
\n  French      - http:\/\/sed.sourceforge.net\/sed1line_fr.html<\/span>
\n  German      - http:\/\/sed.sourceforge.net\/sed1line_de.html<\/span>
\n  Italian     - (pending)<\/span>
\n  Portuguese  - http:\/\/sed.sourceforge.net\/sed1line_pt-BR.html<\/span>
\n  Spanish     - (pending)<\/span>
\n
\n
\nFILE SPACING:<\/span>
\n
\n # double space a file<\/span>
\n sed G<\/span>
\n
\n # double space a file which already has blank lines in it. Output file<\/span>
\n # should contain no more than one blank line between lines of text.<\/span>
\n sed '\/^$\/d;G'<\/span>
\n
\n # triple space a file<\/span>
\n sed 'G;G'<\/span>
\n
\n # undo double-spacing (assumes even-numbered lines are always blank)<\/span>
\n sed 'n;d'<\/span>
\n
\n # insert a blank line above every line which matches \"regex\"<\/span>
\n sed '\/regex\/{x;p;x;}'<\/span>
\n
\n # insert a blank line below every line which matches \"regex\"<\/span>
\n sed '\/regex\/G'<\/span>
\n
\n # insert a blank line above and below every line which matches \"regex\"<\/span>
\n sed '\/regex\/{x;p;x;G;}'<\/span>
\n
\nNUMBERING:<\/span>
\n
\n # number each line of a file (simple left alignment). Using a tab (see<\/span>
\n # note on '\\t' at end of file) instead of space will preserve margins.<\/span>
\n sed = filename | sed 'N;s\/\\n\/\\t\/'<\/span>
\n
\n # number each line of a file (number on left, right-aligned)<\/span>
\n sed = filename | sed 'N; s\/^\/     \/; s\/ *\\(.\\{6,\\}\\)\\n\/\\1  \/'<\/span>
\n
\n # number each line of file, but only print numbers if line is not blank<\/span>
\n sed '\/.\/=' filename | sed '\/.\/N; s\/\\n\/ \/'<\/span>
\n
\n # count lines (emulates \"wc -l\")<\/span>
\n sed -n '$='<\/span>
\n
\nTEXT CONVERSION AND SUBSTITUTION:<\/span>
\n
\n # IN UNIX ENVIRONMENT: convert DOS newlines (CR\/LF) to Unix format.<\/span>
\n sed 's\/.$\/\/'               # assumes that all lines end with CR\/LF<\/span>
\n sed 's\/^M$\/\/'              # in bash\/tcsh, press Ctrl-V then Ctrl-M<\/span>
\n sed 's\/\\x0D$\/\/'            # works on ssed, gsed 3.02.80 or higher<\/span>
\n
\n # IN UNIX ENVIRONMENT: convert Unix newlines (LF) to DOS format.<\/span>
\n sed \"s\/$\/`echo -e \\\\\\r`\/\"            # command line under ksh<\/span>
\n sed 's\/$'\"\/`echo \\\\\\r`\/\"             # command line under bash<\/span>
\n sed \"s\/$\/`echo \\\\\\r`\/\"               # command line under zsh<\/span>
\n sed 's\/$\/\\r\/'                        # gsed 3.02.80 or higher<\/span>
\n
\n # IN DOS ENVIRONMENT: convert Unix newlines (LF) to DOS format.<\/span>
\n sed \"s\/$\/\/\"                          # method 1<\/span>
\n sed -n p                             # method 2<\/span>
\n
\n # IN DOS ENVIRONMENT: convert DOS newlines (CR\/LF) to Unix format.<\/span>
\n # Can only be done with UnxUtils sed, version 4.0.7 or higher. The<\/span>
\n # UnxUtils version can be identified by the custom \"--text\" switch<\/span>
\n # which appears when you use the \"--help\" switch. Otherwise, changing<\/span>
\n # DOS newlines to Unix newlines cannot be done with sed in a DOS<\/span>
\n # environment. Use \"tr\" instead.<\/span>
\n sed \"s\/\\r\/\/\" infile >outfile         # UnxUtils sed v4.0.7 or higher<\/span>
\n tr -d \\r <infile >outfile            # GNU tr version 1.22 or higher<\/span>
\n
\n # delete leading whitespace (spaces, tabs) from front of each line<\/span>
\n # aligns all text flush left<\/span>
\n sed 's\/^[ \\t]*\/\/'                    # see note on '\\t' at end of file<\/span>
\n
\n # delete trailing whitespace (spaces, tabs) from end of each line<\/span>
\n sed 's\/[ \\t]*$\/\/'                    # see note on '\\t' at end of file<\/span>
\n
\n # delete BOTH leading and trailing whitespace from each line<\/span>
\n sed 's\/^[ \\t]*\/\/;s\/[ \\t]*$\/\/'<\/span>
\n
\n # insert 5 blank spaces at beginning of each line (make page offset)<\/span>
\n sed 's\/^\/     \/'<\/span>
\n
\n # align all text flush right on a 79-column width<\/span>
\n sed -e :a -e 's\/^.\\{1,78\\}$\/ &\/;ta'  # set at 78 plus 1 space<\/span>
\n
\n # center all text in the middle of 79-column width. In method 1,<\/span>
\n # spaces at the beginning of the line are significant, and trailing<\/span>
\n # spaces are appended at the end of the line. In method 2, spaces at<\/span>
\n # the beginning of the line are discarded in centering the line, and<\/span>
\n # no trailing spaces appear at the end of lines.<\/span>
\n sed  -e :a -e 's\/^.\\{1,77\\}$\/ & \/;ta'                     # method 1<\/span>
\n sed  -e :a -e 's\/^.\\{1,77\\}$\/ &\/;ta' -e 's\/\\( *\\)\\1\/\\1\/'  # method 2<\/span>
\n
\n # substitute (find and replace) \"foo\" with \"bar\" on each line<\/span>
\n sed 's\/foo\/bar\/'             # replaces only 1st instance in a line<\/span>
\n sed 's\/foo\/bar\/4'            # replaces only 4th instance in a line<\/span>
\n sed 's\/foo\/bar\/g'            # replaces ALL instances in a line<\/span>
\n sed 's\/\\(.*\\)foo\\(.*foo\\)\/\\1bar\\2\/' # replace the next-to-last case<\/span>
\n sed 's\/\\(.*\\)foo\/\\1bar\/'            # replace only the last case<\/span>
\n
\n # substitute \"foo\" with \"bar\" ONLY for lines which contain \"baz\"<\/span>
\n sed '\/baz\/s\/foo\/bar\/g'<\/span>
\n
\n # substitute \"foo\" with \"bar\" EXCEPT for lines which contain \"baz\"<\/span>
\n sed '\/baz\/!s\/foo\/bar\/g'<\/span>
\n
\n # change \"scarlet\" or \"ruby\" or \"puce\" to \"red\"<\/span>
\n sed 's\/scarlet\/red\/g;s\/ruby\/red\/g;s\/puce\/red\/g'   # most seds<\/span>
\n gsed 's\/scarlet\\|ruby\\|puce\/red\/g'                # GNU sed only<\/span>
\n
\n # reverse order of lines (emulates \"tac\")<\/span>
\n # bug\/feature in HHsed v1.5 causes blank lines to be deleted<\/span>
\n sed '1!G;h;$!d'               # method 1<\/span>
\n sed -n '1!G;h;$p'             # method 2<\/span>
\n
\n # reverse each character on the line (emulates \"rev\")<\/span>
\n sed '\/\\n\/!G;s\/\\(.\\)\\(.*\\n\\)\/&\\2\\1\/;\/\/D;s\/.\/\/'<\/span>
\n
\n # join pairs of lines side-by-side (like \"paste\")<\/span>
\n sed '$!N;s\/\\n\/ \/'<\/span>
\n
\n # if a line ends with a backslash, append the next line to it<\/span>
\n sed -e :a -e '\/\\\\$\/N; s\/\\\\\\n\/\/; ta'<\/span>
\n
\n # if a line begins with an equal sign, append it to the previous line<\/span>
\n # and replace the \"=\" with a single space<\/span>
\n sed -e :a -e '$!N;s\/\\n=\/ \/;ta' -e 'P;D'<\/span>
\n
\n # add commas to numeric strings, changing \"1234567\" to \"1,234,567\"<\/span>
\n gsed ':a;s\/\\B[0-9]\\{3\\}\\>\/,&\/;ta'                     # GNU sed<\/span>
\n sed -e :a -e 's\/\\(.*[0-9]\\)\\([0-9]\\{3\\}\\)\/\\1,\\2\/;ta'  # other seds<\/span>
\n
\n # add commas to numbers with decimal points and minus signs (GNU sed)<\/span>
\n gsed -r ':a;s\/(^|[^0-9.])([0-9]+)([0-9]{3})\/\\1\\2,\\3\/g;ta'<\/span>
\n
\n # add a blank line every 5 lines (after lines 5, 10, 15, 20, etc.)<\/span>
\n gsed '0~5G'                  # GNU sed only<\/span>
\n sed 'n;n;n;n;G;'             # other seds<\/span>
\n
\nSELECTIVE PRINTING OF CERTAIN LINES:<\/span>
\n
\n # print first 10 lines of file (emulates behavior of \"head\")<\/span>
\n sed 10q<\/span>
\n
\n # print first line of file (emulates \"head -1\")<\/span>
\n sed q<\/span>
\n
\n # print the last 10 lines of a file (emulates \"tail\")<\/span>
\n sed -e :a -e '$q;N;11,$D;ba'<\/span>
\n
\n # print the last 2 lines of a file (emulates \"tail -2\")<\/span>
\n sed '$!N;$!D'<\/span>
\n
\n # print the last line of a file (emulates \"tail -1\")<\/span>
\n sed '$!d'                    # method 1<\/span>
\n sed -n '$p'                  # method 2<\/span>
\n
\n # print the next-to-the-last line of a file<\/span>
\n sed -e '$!{h;d;}' -e x              # for 1-line files, print blank line<\/span>
\n sed -e '1{$q;}' -e '$!{h;d;}' -e x  # for 1-line files, print the line<\/span>
\n sed -e '1{$d;}' -e '$!{h;d;}' -e x  # for 1-line files, print nothing<\/span>
\n
\n # print only lines which match regular expression (emulates \"grep\")<\/span>
\n sed -n '\/regexp\/p'           # method 1<\/span>
\n sed '\/regexp\/!d'             # method 2<\/span>
\n
\n # print only lines which do NOT match regexp (emulates \"grep -v\")<\/span>
\n sed -n '\/regexp\/!p'          # method 1, corresponds to above<\/span>
\n sed '\/regexp\/d'              # method 2, simpler syntax<\/span>
\n
\n # print the line immediately before a regexp, but not the line<\/span>
\n # containing the regexp<\/span>
\n sed -n '\/regexp\/{g;1!p;};h'<\/span>
\n
\n # print the line immediately after a regexp, but not the line<\/span>
\n # containing the regexp<\/span>
\n sed -n '\/regexp\/{n;p;}'<\/span>
\n
\n # print 1 line of context before and after regexp, with line number<\/span>
\n # indicating where the regexp occurred (similar to \"grep -A1 -B1\")<\/span>
\n sed -n -e '\/regexp\/{=;x;1!p;g;$!N;p;D;}' -e h<\/span>
\n
\n # grep for AAA and BBB and CCC (in any order)<\/span>
\n sed '\/AAA\/!d; \/BBB\/!d; \/CCC\/!d'<\/span>
\n
\n # grep for AAA and BBB and CCC (in that order)<\/span>
\n sed '\/AAA.*BBB.*CCC\/!d'<\/span>
\n
\n # grep for AAA or BBB or CCC (emulates \"egrep\")<\/span>
\n sed -e '\/AAA\/b' -e '\/BBB\/b' -e '\/CCC\/b' -e d    # most seds<\/span>
\n gsed '\/AAA\\|BBB\\|CCC\/!d'                        # GNU sed only<\/span>
\n
\n # print paragraph if it contains AAA (blank lines separate paragraphs)<\/span>
\n # HHsed v1.5 must insert a 'G;' after 'x;' in the next 3 scripts below<\/span>
\n sed -e '\/.\/{H;$!d;}' -e 'x;\/AAA\/!d;'<\/span>
\n
\n # print paragraph if it contains AAA and BBB and CCC (in any order)<\/span>
\n sed -e '\/.\/{H;$!d;}' -e 'x;\/AAA\/!d;\/BBB\/!d;\/CCC\/!d'<\/span>
\n
\n # print paragraph if it contains AAA or BBB or CCC<\/span>
\n sed -e '\/.\/{H;$!d;}' -e 'x;\/AAA\/b' -e '\/BBB\/b' -e '\/CCC\/b' -e d<\/span>
\n gsed '\/.\/{H;$!d;};x;\/AAA\\|BBB\\|CCC\/b;d'         # GNU sed only<\/span>
\n
\n # print only lines of 65 characters or longer<\/span>
\n sed -n '\/^.\\{65\\}\/p'<\/span>
\n
\n # print only lines of less than 65 characters<\/span>
\n sed -n '\/^.\\{65\\}\/!p'        # method 1, corresponds to above<\/span>
\n sed '\/^.\\{65\\}\/d'            # method 2, simpler syntax<\/span>
\n
\n # print section of file from regular expression to end of file<\/span>
\n sed -n '\/regexp\/,$p'<\/span>
\n
\n # print section of file based on line numbers (lines 8-12, inclusive)<\/span>
\n sed -n '8,12p'               # method 1<\/span>
\n sed '8,12!d'                 # method 2<\/span>
\n
\n # print line number 52<\/span>
\n sed -n '52p'                 # method 1<\/span>
\n sed '52!d'                   # method 2<\/span>
\n sed '52q;d'                  # method 3, efficient on large files<\/span>
\n
\n # beginning at line 3, print every 7th line<\/span>
\n gsed -n '3~7p'               # GNU sed only<\/span>
\n sed -n '3,${p;n;n;n;n;n;n;}' # other seds<\/span>
\n
\n # print section of file between two regular expressions (inclusive)<\/span>
\n sed -n '\/Iowa\/,\/Montana\/p'             # case sensitive<\/span>
\n
\nSELECTIVE DELETION OF CERTAIN LINES:<\/span>
\n
\n # print all of file EXCEPT section between 2 regular expressions<\/span>
\n sed '\/Iowa\/,\/Montana\/d'<\/span>
\n
\n # delete duplicate, consecutive lines from a file (emulates \"uniq\").<\/span>
\n # First line in a set of duplicate lines is kept, rest are deleted.<\/span>
\n sed '$!N; \/^\\(.*\\)\\n\\1$\/!P; D'<\/span>
\n
\n # delete duplicate, nonconsecutive lines from a file. Beware not to<\/span>
\n # overflow the buffer size of the hold space, or else use GNU sed.<\/span>
\n sed -n 'G; s\/\\n\/&&\/; \/^\\([ -~]*\\n\\).*\\n\\1\/d; s\/\\n\/\/; h; P'<\/span>
\n
\n # delete all lines except duplicate lines (emulates \"uniq -d\").<\/span>
\n sed '$!N; s\/^\\(.*\\)\\n\\1$\/\\1\/; t; D'<\/span>
\n
\n # delete the first 10 lines of a file<\/span>
\n sed '1,10d'<\/span>
\n
\n # delete the last line of a file<\/span>
\n sed '$d'<\/span>
\n
\n # delete the last 2 lines of a file<\/span>
\n sed 'N;$!P;$!D;$d'<\/span>
\n
\n # delete the last 10 lines of a file<\/span>
\n sed -e :a -e '$d;N;2,10ba' -e 'P;D'   # method 1<\/span>
\n sed -n -e :a -e '1,10!{P;N;D;};N;ba'  # method 2<\/span>
\n
\n # delete every 8th line<\/span>
\n gsed '0~8d'                           # GNU sed only<\/span>
\n sed 'n;n;n;n;n;n;n;d;'                # other seds<\/span>
\n
\n # delete lines matching pattern<\/span>
\n sed '\/pattern\/d'<\/span>
\n
\n # delete ALL blank lines from a file (same as \"grep '.' \")<\/span>
\n sed '\/^$\/d'                           # method 1<\/span>
\n sed '\/.\/!d'                           # method 2<\/span>
\n
\n # delete all CONSECUTIVE blank lines from file except the first; also<\/span>
\n # deletes all blank lines from top and end of file (emulates \"cat -s\")<\/span>
\n sed '\/.\/,\/^$\/!d'          # method 1, allows 0 blanks at top, 1 at EOF<\/span>
\n sed '\/^$\/N;\/\\n$\/D'        # method 2, allows 1 blank at top, 0 at EOF<\/span>
\n
\n # delete all CONSECUTIVE blank lines from file except the first 2:<\/span>
\n sed '\/^$\/N;\/\\n$\/N;\/\/D'<\/span>
\n
\n # delete all leading blank lines at top of file<\/span>
\n sed '\/.\/,$!d'<\/span>
\n
\n # delete all trailing blank lines at end of file<\/span>
\n sed -e :a -e '\/^\\n*$\/{$d;N;ba' -e '}'  # works on all seds<\/span>
\n sed -e :a -e '\/^\\n*$\/N;\/\\n$\/ba'        # ditto, except for gsed 3.02.*<\/span>
\n
\n # delete the last line of each paragraph<\/span>
\n sed -n '\/^$\/{p;h;};\/.\/{x;\/.\/p;}'<\/span>
\n
\nSPECIAL APPLICATIONS:<\/span>
\n
\n # remove nroff overstrikes (char, backspace) from man pages. The 'echo'<\/span>
\n # command may need an -e switch if you use Unix System V or bash shell.<\/span>
\n sed \"s\/.`echo \\\\\\b`\/\/g\"    # double quotes required for Unix environment<\/span>
\n sed 's\/.^H\/\/g'             # in bash\/tcsh, press Ctrl-V and then Ctrl-H<\/span>
\n sed 's\/.\\x08\/\/g'           # hex expression for sed 1.5, GNU sed, ssed<\/span>
\n
\n # get Usenet\/e-mail message header<\/span>
\n sed '\/^$\/q'                # deletes everything after first blank line<\/span>
\n
\n # get Usenet\/e-mail message body<\/span>
\n sed '1,\/^$\/d'              # deletes everything up to first blank line<\/span>
\n
\n # get Subject header, but remove initial \"Subject: \" portion<\/span>
\n sed '\/^Subject: *\/!d; s\/\/\/;q'<\/span>
\n
\n # get return address header<\/span>
\n sed '\/^Reply-To:\/q; \/^From:\/h; \/.\/d;g;q'<\/span>
\n
\n # parse out the address proper. Pulls out the e-mail address by itself<\/span>
\n # from the 1-line return address header (see preceding script)<\/span>
\n sed 's\/ *(.*)\/\/; s\/>.*\/\/; s\/.*[:<] *\/\/'<\/span>
\n
\n # add a leading angle bracket and space to each line (quote a message)<\/span>
\n sed 's\/^\/> \/'<\/span>
\n
\n # delete leading angle bracket & space from each line (unquote a message)<\/span>
\n sed 's\/^> \/\/'<\/span>
\n
\n # remove most HTML tags (accommodates multiple-line tags)<\/span>
\n sed -e :a -e 's\/<[^>]*>\/\/g;\/<\/N;\/\/ba'<\/span>
\n
\n # extract multi-part uuencoded binaries, removing extraneous header<\/span>
\n # info, so that only the uuencoded portion remains. Files passed to<\/span>
\n # sed must be passed in the proper order. Version 1 can be entered<\/span>
\n # from the command line; version 2 can be made into an executable<\/span>
\n # Unix shell script. (Modified from a script by Rahul Dhesi.)<\/span>
\n sed '\/^end\/,\/^begin\/d' file1 file2 ... fileX | uudecode   # vers. 1<\/span>
\n sed '\/^end\/,\/^begin\/d' \"$@\" | uudecode                    # vers. 2<\/span>
\n
\n # sort paragraphs of file alphabetically. Paragraphs are separated by blank<\/span>
\n # lines. GNU sed uses \\v for vertical tab, or any unique char will do.<\/span>
\n sed '\/.\/{H;d;};x;s\/\\n\/={NL}=\/g' file | sort | sed '1s\/={NL}=\/\/;s\/={NL}=\/\\n\/g'<\/span>
\n gsed '\/.\/{H;d};x;y\/\\n\/\\v\/' file | sort | sed '1s\/\\v\/\/;y\/\\v\/\\n\/'<\/span>
\n
\n # zip up each .TXT file individually, deleting the source file and<\/span>
\n # setting the name of each .ZIP file to the basename of the .TXT file<\/span>
\n # (under DOS: the \"dir \/b\" switch returns bare filenames in all caps).<\/span>
\n echo @echo off >zipup.bat<\/span>
\n dir \/b *.txt | sed \"s\/^\\(.*\\)\\.TXT\/pkzip -mo \\1 \\1.TXT\/\" >>zipup.bat<\/span>
\n
\nTYPICAL USE: Sed takes one or more editing commands and applies all of<\/span>
\nthem, in sequence, to each line of input. After all the commands have<\/span>
\nbeen applied to the first input line, that line is output and a second<\/span>
\ninput line is taken for processing, and the cycle repeats. The<\/span>
\npreceding examples assume that input comes from the standard input<\/span>
\ndevice (i.e, the console, normally this will be piped input). One or<\/span>
\nmore filenames can be appended to the command line if the input does<\/span>
\nnot come from stdin. Output is sent to stdout (the screen). Thus:<\/span>
\n
\n cat filename | sed '10q'        # uses piped input<\/span>
\n sed '10q' filename              # same effect, avoids a useless \"cat\"<\/span>
\n sed '10q' filename > newfile    # redirects output to disk<\/span>
\n
\nFor additional syntax instructions, including the way to apply editing<\/span>
\ncommands from a disk file instead of the command line, consult \"sed &<\/span>
\nawk, 2nd Edition,\" by Dale Dougherty and Arnold Robbins (O'Reilly,<\/span>
\n1997; http:\/\/www.ora.com), \"UNIX Text Processing,\" by Dale Dougherty<\/span>
\nand Tim O'Reilly (Hayden Books, 1987) or the tutorials by Mike Arst<\/span>
\ndistributed in U-SEDIT2.ZIP (many sites). To fully exploit the power<\/span>
\nof sed, one must understand \"regular expressions.\" For this, see<\/span>
\n\"Mastering Regular Expressions\" by Jeffrey Friedl (O'Reilly, 1997).<\/span>
\nThe manual (\"man\") pages on Unix systems may be helpful (try \"man<\/span>
\nsed\", \"man regexp\", or the subsection on regular expressions in \"man<\/span>
\ned\"), but man pages are notoriously difficult. They are not written to<\/span>
\nteach sed use or regexps to first-time users, but as a reference text<\/span>
\nfor those already acquainted with these tools.<\/span>
\n
\nQUOTING SYNTAX: The preceding examples use single quotes ('...')<\/span>
\ninstead of double quotes (\"...\") to enclose editing commands, since<\/span>
\nsed is typically used on a Unix platform. Single quotes prevent the<\/span>
\nUnix shell from intrepreting the dollar sign ($) and backquotes<\/span>
\n(`...`), which are expanded by the shell if they are enclosed in<\/span>
\ndouble quotes. Users of the \"csh\" shell and derivatives will also need<\/span>
\nto quote the exclamation mark (!) with the backslash (i.e., \\!) to<\/span>
\nproperly run the examples listed above, even within single quotes.<\/span>
\nVersions of sed written for DOS invariably require double quotes<\/span>
\n(\"...\") instead of single quotes to enclose editing commands.<\/span>
\n
\nUSE OF '\\t' IN SED SCRIPTS: For clarity in documentation, we have used<\/span>
\nthe expression '\\t' to indicate a tab character (0x09) in the scripts.<\/span>
\nHowever, most versions of sed do not recognize the '\\t' abbreviation,<\/span>
\nso when typing these scripts from the command line, you should press<\/span>
\nthe TAB key instead. '\\t' is supported as a regular expression<\/span>
\nmetacharacter in awk, perl, and HHsed, sedmod, and GNU sed v3.02.80.<\/span>
\n
\nVERSIONS OF SED: Versions of sed do differ, and some slight syntax<\/span>
\nvariation is to be expected. In particular, most do not support the<\/span>
\nuse of labels (:name) or branch instructions (b,t) within editing<\/span>
\ncommands, except at the end of those commands. We have used the syntax<\/span>
\nwhich will be portable to most users of sed, even though the popular<\/span>
\nGNU versions of sed allow a more succinct syntax. When the reader sees<\/span>
\na fairly long command such as this:<\/span>
\n
\n   sed -e '\/AAA\/b' -e '\/BBB\/b' -e '\/CCC\/b' -e d<\/span>
\n
\nit is heartening to know that GNU sed will let you reduce it to:<\/span>
\n
\n   sed '\/AAA\/b;\/BBB\/b;\/CCC\/b;d'      # or even<\/span>
\n   sed '\/AAA\\|BBB\\|CCC\/b;d'<\/span>
\n
\nIn addition, remember that while many versions of sed accept a command<\/span>
\nlike \"\/one\/ s\/RE1\/RE2\/\", some do NOT allow \"\/one\/! s\/RE1\/RE2\/\", which<\/span>
\ncontains space before the 's'. Omit the space when typing the command.<\/span>
\n
\nOPTIMIZING FOR SPEED: If execution speed needs to be increased (due to<\/span>
\nlarge input files or slow processors or hard disks), substitution will<\/span>
\nbe executed more quickly if the \"find\" expression is specified before<\/span>
\ngiving the \"s\/...\/...\/\" instruction. Thus:<\/span>
\n
\n   sed 's\/foo\/bar\/g' filename         # standard replace command<\/span>
\n   sed '\/foo\/ s\/foo\/bar\/g' filename   # executes more quickly<\/span>
\n   sed '\/foo\/ s\/\/bar\/g' filename      # shorthand sed syntax<\/span>
\n
\nOn line selection or deletion in which you only need to output lines<\/span>
\nfrom the first part of the file, a \"quit\" command (q) in the script<\/span>
\nwill drastically reduce processing time for large files. Thus:<\/span>
\n
\n   sed -n '45,50p' filename           # print line nos. 45-50 of a file<\/span>
\n   sed -n '51q;45,50p' filename       # same, but executes much faster<\/span>
\n
\nIf you have any additional scripts to contribute or if you find errors<\/span>
\nin this document, please send e-mail to the compiler. Indicate the<\/span>
\nversion of sed you used, the operating system it was compiled for, and<\/span>
\nthe nature of the problem. To qualify as a one-liner, the command line<\/span>
\nmust be 65 characters or less. Various scripts in this file have been<\/span>
\nwritten or contributed by:<\/span>
\n
\n Al Aab                   # founder of \"seders\" list<\/span>
\n Edgar Allen              # various<\/span>
\n Yiorgos Adamopoulos      # various<\/span>
\n Dale Dougherty           # author of \"sed & awk\"<\/span>
\n Carlos Duarte            # author of \"do it with sed\"<\/span>
\n Eric Pement              # author of this document<\/span>
\n Ken Pizzini              # author of GNU sed v3.02<\/span>
\n S.G. Ravenhall           # great de-html script<\/span>
\n Greg Ubben               # many contributions & much help<\/span>
\n-------------------------------------------------------------------------<\/span>
\n
\n","protected":false},"excerpt":{"rendered":"

————————————————————————- USEFUL ONE-LINE SCRIPTS FOR SED (Unix stream editor)        Dec. 29, 2005 Compiled by Eric Pement – pemente[at]northpark[dot]edu        version 5.5 Latest version of this file (in English) is usually at:    http:\/\/sed.sourceforge.net\/sed1line.txt    http:\/\/www.pement.org\/sed\/sed1line.txt This file will also available in other languages:   Chinese     – http:\/\/sed.sourceforge.net\/sed1line_zh-CN.html   Czech       – http:\/\/sed.sourceforge.net\/sed1line_cz.html   Dutch       – http:\/\/sed.sourceforge.net\/sed1line_nl.html   […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_import_markdown_pro_load_document_selector":0,"_import_markdown_pro_submit_text_textarea":"","site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"categories":[39],"tags":[],"class_list":["post-362","post","type-post","status-publish","format-standard","hentry","category-os_linux_unix_macos"],"_links":{"self":[{"href":"https:\/\/hasu0707.duckdns.org\/blog\/index.php?rest_route=\/wp\/v2\/posts\/362","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/hasu0707.duckdns.org\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/hasu0707.duckdns.org\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/hasu0707.duckdns.org\/blog\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/hasu0707.duckdns.org\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=362"}],"version-history":[{"count":0,"href":"https:\/\/hasu0707.duckdns.org\/blog\/index.php?rest_route=\/wp\/v2\/posts\/362\/revisions"}],"wp:attachment":[{"href":"https:\/\/hasu0707.duckdns.org\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=362"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/hasu0707.duckdns.org\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=362"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/hasu0707.duckdns.org\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=362"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}