Lines Matching refs:sed

6   Section 4.55: sed - Stream editor
13 undocumented inconsistencies between the historical versions of sed and
15 implementing a POSIX-compatible version of sed, and should not be
19  1.	32V and BSD derived implementations of sed strip the text
23 	#!/bin/sed -f
36 	sed do not do this stripping.  The argument against stripping is
37 	that it is difficult to write sed scripts that have leading blanks
39 	difficult to write readable sed scripts unless indentation is allowed
44  2.	Historical versions of sed required that the w flag be the last
48  3.	Historical versions of sed required that whitespace follow a w
52  4.	Historical versions of sed permitted any number of whitespace
59 	for backslash.  Some historical versions of sed displayed two
81  8.	Historic versions of sed permitted commands to be separated
82 	by semi-colons, e.g. 'sed -ne '1p;2p;3q' printed the first
89  9.	Historic versions of sed terminated the script if EOF was reached
92 	sed -e '
136 14.	POSIX does not explicitly specify how sed behaves if no script is
137 	specified.  Since the sed Synopsis permits this form of the command,
140 	command.  Historic sed implementations behave differently for "ls |
141 	sed", where they produce no output, and "ls | sed -e#", where they
145 	sed behave nonintuitively when the w commands are preceded by
154 	POSIX would be that "echo xyz | sed s/./\a" would display "\ayz".
155 	As historic sed implementations always discarded the backslash,
161 	of sed.
165 	Historic implementations of sed assigned different locations to
183 22.	Historic implementations of sed ignore the RE delimiter characters
192 		sed -e /abc/s//XXX/