Lines Matching full:sed

4   Section 4.55: sed - Stream editor
11 undocumented inconsistencies between the historical versions of sed and
13 implementing a POSIX-compatible version of sed, and should not be
17  1.	32V and BSD derived implementations of sed strip the text
21 	#!/bin/sed -f
34 	sed do not do this stripping.  The argument against stripping is
35 	that it is difficult to write sed scripts that have leading blanks
37 	difficult to write readable sed scripts unless indentation is allowed
42  2.	Historical versions of sed required that the w flag be the last
46  3.	Historical versions of sed required that whitespace follow a w
50  4.	Historical versions of sed permitted any number of whitespace
57 	for backslash.  Some historical versions of sed displayed two
79  8.	Historic versions of sed permitted commands to be separated
80 	by semi-colons, e.g. 'sed -ne '1p;2p;3q' printed the first
87  9.	Historic versions of sed terminated the script if EOF was reached
90 	sed -e '
134 14.	POSIX does not explicitly specify how sed behaves if no script is
135 	specified.  Since the sed Synopsis permits this form of the command,
138 	command.  Historic sed implementations behave differently for "ls |
139 	sed", where they produce no output, and "ls | sed -e#", where they
143 	sed behave nonintuitively when the w commands are preceded by
152 	POSIX would be that "echo xyz | sed s/./\a" would display "\ayz".
153 	As historic sed implementations always discarded the backslash,
159 	of sed.
163 	Historic implementations of sed assigned different locations to
181 22.	Historic implementations of sed ignore the RE delimiter characters
190 		sed -e /abc/s//XXX/