busybox/testsuite/sed.tests

#!/bin/sh

# SUSv3 compliant sed tests.
# Copyright 2005 by Rob Landley <rob@landley.net>
# Licensed under GPL v2, see file LICENSE for details.

. ./testing.sh

# testing "description" "arguments" "result" "infile" "stdin"

# Corner cases
testing "sed no files (stdin)" 'sed ""' "hello\n" "" "hello\n"
testing "sed explicit stdin" 'sed "" -' "hello\n" "" "hello\n"
testing "sed handles empty lines" "sed -e 's/\$/@/'" "@\n" "" "\n"
testing "sed stdin twice" 'sed "" - -' "hello" "" "hello"

# Trailing EOF.
#	Match $, at end of each file or all files?

# -e corner cases
#	without -e
#	multiple -e
#		interact with a
#	-eee arg1 arg2 arg3
# -f corner cases
#	-e -f -e
# -n corner cases
#	no newline at EOF?
# -r corner cases
#	Just make sure it works.
# -i corner cases:
#	sed -i -
#	permissions
#	-i on a symlink
#	on a directory
#       With $ last-line test
# Continue with \
#       End of script with trailing \

# command list
testing "sed accepts blanks before command" "sed -e '1 d'" "" "" ""
testing "sed accepts newlines in -e" "sed -e 'i\
1
a\
3'" "1\n2\n3\n" "" "2\n"
testing "sed accepts multiple -e" "sed -e 'i\' -e '1' -e 'a\' -e '3'" \
	"1\n2\n3\n" "" "2\n"

# substitutions
testing "sed -n" "sed -n -e s/foo/bar/ -e s/bar/baz/" "" "" "foo\n"
testing "sed s//p" "sed -e s/foo/bar/p -e s/bar/baz/p" "bar\nbaz\nbaz\n" \
	"" "foo\n"
testing "sed -n s//p" "sed -ne s/abc/def/p" "def\n" "" "abc\n"
test x"$SKIP_KNOWN_BUGS" = x"" && {
testing "sed s//g (exhaustive)" "sed -e 's/[[:space:]]*/,/g'" ",1,2,3,4,5,\n" \
	"" "12345\n"
}
testing "sed s arbitrary delimiter" "sed -e 's woo boing '" "boing\n" "" "woo\n"
testing "sed s chains" "sed -e s/foo/bar/ -e s/bar/baz/" "baz\n" "" "foo\n"
testing "sed s chains2" "sed -e s/foo/bar/ -e s/baz/nee/" "bar\n" "" "foo\n"
testing "sed s [delimiter]" "sed -e 's@[@]@@'" "onetwo" "" "one@two"
testing "sed s with \\t (GNU ext)" "sed 's/\t/ /'" "one two" "" "one\ttwo"

# branch
testing "sed b (branch)" "sed -e 'b one;p;: one'" "foo\n" "" "foo\n"
testing "sed b (branch with no label jumps to end)" "sed -e 'b;p'" \
	"foo\n" "" "foo\n"

# test and branch
testing "sed t (test/branch)" "sed -e 's/a/1/;t one;p;: one;p'" \
	"1\n1\nb\nb\nb\nc\nc\nc\n" "" "a\nb\nc\n"
testing "sed t (test/branch clears test bit)" "sed -e 's/a/b/;:loop;t loop'" \
	"b\nb\nc\n" "" "a\nb\nc\n"
testing "sed T (!test/branch)" "sed -e 's/a/1/;T notone;p;: notone;p'" \
	"1\n1\n1\nb\nb\nc\nc\n" "" "a\nb\nc\n"

test x"$SKIP_KNOWN_BUGS" = x"" && {
# Normal sed end-of-script doesn't print "c" because n flushed the pattern
# space.  If n hits EOF, pattern space is empty when script ends.
# Query: how does this interact with no newline at EOF?
testing "sed n (flushes pattern space, terminates early)" "sed -e 'n;p'" \
	"a\nb\nb\nc\n" "" "a\nb\nc\n"
# N does _not_ flush pattern space, therefore c is still in there @ script end.
testing "sed N (doesn't flush pattern space when terminating)" "sed -e 'N;p'" \
	"a\nb\na\nb\nc\n" "" "a\nb\nc\n"
}
testing "sed address match newline" 'sed "/b/N;/b\\nc/i woo"' \
	"a\nwoo\nb\nc\nd\n" "" "a\nb\nc\nd\n"

# Multiple lines in pattern space
testing "sed N (stops at end of input) and P (prints to first newline only)" \
	"sed -n 'N;P;p'" "a\na\nb\n" "" "a\nb\nc\n"

# Hold space
testing "sed G (append hold space to pattern space)" 'sed G' "a\n\nb\n\nc\n\n" \
	"" "a\nb\nc\n"
#testing "sed g/G (swap/append hold and patter space)"
#testing "sed g (swap hold/pattern space)"

testing "sed d ends script iteration" \
	"sed -e '/ook/d;s/ook/ping/p;i woot'" "" "" "ook\n"
testing "sed d ends script iteration (2)" \
	"sed -e '/ook/d;a\' -e 'bang'" "woot\nbang\n" "" "ook\nwoot\n"

# Multiple files, with varying newlines and NUL bytes
test x"$SKIP_KNOWN_BUGS" = x"" && {
testing "sed embedded NUL" "sed -e 's/woo/bang/'" "\0bang\0woo\0" "" \
	"\0woo\0woo\0"
}
testing "sed embedded NUL g" "sed -e 's/woo/bang/g'" "bang\0bang\0" "" \
	"woo\0woo\0"
test x"$SKIP_KNOWN_BUGS" = x"" && {
echo -e "/woo/a he\0llo" > sed.commands
testing "sed NUL in command" "sed -f sed.commands" "woo\nhe\0llo\n" "" "woo"
rm sed.commands
}

# sed has funky behavior with newlines at the end of file.  Test lots of
# corner cases with the optional newline appending behavior.

testing "sed normal newlines" "sed -e 's/woo/bang/' input -" "bang\nbang\n" \
	"woo\n" "woo\n"
testing "sed leave off trailing newline" "sed -e 's/woo/bang/' input -" \
	"bang\nbang" "woo\n" "woo"
testing "sed autoinsert newline" "sed -e 's/woo/bang/' input -" "bang\nbang" \
	"woo" "woo"
testing "sed empty file plus cat" "sed -e 's/nohit//' input -" "one\ntwo" \
	"" "one\ntwo"
testing "sed cat plus empty file" "sed -e 's/nohit//' input -" "one\ntwo" \
	"one\ntwo" ""
test x"$SKIP_KNOWN_BUGS" = x"" && {
testing "sed append autoinserts newline" "sed -e '/woot/a woo' -" \
	"woot\nwoo\n" "" "woot"
}
testing "sed insert doesn't autoinsert newline" "sed -e '/woot/i woo' -" \
	"woo\nwoot" "" "woot"
testing "sed print autoinsert newlines" "sed -e 'p' -" "one\none" "" "one"
testing "sed print autoinsert newlines two files" "sed -e 'p' input -" \
	"one\none\ntwo\ntwo" "one" "two"
testing "sed noprint, no match, no newline" "sed -ne 's/woo/bang/' input" \
	"" "no\n" ""
testing "sed selective matches with one nl" "sed -ne 's/woo/bang/p' input -" \
	"a bang\nc bang\n" "a woo\nb no" "c woo\nd no"
testing "sed selective matches insert newline" \
	"sed -ne 's/woo/bang/p' input -" "a bang\nb bang\nd bang" \
	"a woo\nb woo" "c no\nd woo"
testing "sed selective matches noinsert newline" \
	"sed -ne 's/woo/bang/p' input -" "a bang\nb bang" "a woo\nb woo" \
	"c no\nd no"
test x"$SKIP_KNOWN_BUGS" = x"" && {
testing "sed clusternewline" \
	"sed -e '/one/a 111' -e '/two/i 222' -e p input -" \
	"one\none\n111\n222\ntwo\ntwo" "one" "two"
}
testing "sed subst+write" \
	"sed -e 's/i/z/' -e 'woutputw' input -; echo -n X; cat outputw" \
	"thzngy\nagaznXthzngy\nagazn" "thingy" "again"
rm outputw
testing "sed trailing NUL" \
	"sed 's/i/z/' input -" \
	"a\0b\0\nc" "a\0b\0" "c"
testing "sed escaped newline in command" \
	"sed 's/a/z\\
z/' input" \
	"z\nz" "a" ""

# Test end-of-file matching behavior

testing "sed match EOF" "sed -e '"'$p'"'" "hello\nthere\nthere" "" \
	"hello\nthere"
testing "sed match EOF two files" "sed -e '"'$p'"' input -" \
	"one\ntwo\nthree\nfour\nfour" "one\ntwo" "three\nfour"
# sed match EOF inline: gnu sed 4.1.5 outputs this:
#00000000  6f 6e 65 0a 6f 6f 6b 0a  6f 6f 6b 0a 74 77 6f 0a  |one.ook.ook.two.|
#00000010  0a 74 68 72 65 65 0a 6f  6f 6b 0a 6f 6f 6b 0a 66  |.three.ook.ook.f|
#00000020  6f 75 72                                          |our|
# which looks buggy to me.
$ECHO -ne "three\nfour" > input2
testing "sed match EOF inline" \
	"sed -e '"'$i ook'"' -i input input2 && cat input input2" \
	"one\nook\ntwothree\nook\nfour" "one\ntwo" ""
rm input2

# Test lie-to-autoconf

testing "sed lie-to-autoconf" "sed --version | grep -o 'GNU sed version '" \
	"GNU sed version \n" "" ""

# Jump to nonexistent label
test x"$SKIP_KNOWN_BUGS" = x"" && {
# Incompatibility: illegal jump is not detected if input is ""
# (that is, no lines at all). GNU sed 4.1.5 complains even in this case
testing "sed nonexistent label" "sed -e 'b walrus' 2>/dev/null || echo yes" \
	"yes\n" "" ""
}

testing "sed backref from empty s uses range regex" \
	"sed -e '/woot/s//eep \0 eep/'" "eep woot eep" "" "woot"

testing "sed backref from empty s uses range regex with newline" \
	"sed -e '/woot/s//eep \0 eep/'" "eep woot eep\n" "" "woot\n"

# -i with no filename

touch ./-  # Detect gnu failure mode here.
testing "sed -i with no arg [GNUFAIL]" "sed -e '' -i 2> /dev/null || echo yes" \
	"yes\n" "" ""
rm ./-     # Clean up

testing "sed s/xxx/[/" "sed -e 's/xxx/[/'" "[\n" "" "xxx\n"

# Ponder this a bit more, why "woo not found" from gnu version?
#testing "sed doesn't substitute in deleted line" \
#	"sed -e '/ook/d;s/ook//;t woo;a bang;'" "bang" "" "ook\n"

# This makes both seds very unhappy.  Why?
#testing "sed -g (exhaustive)" "sed -e 's/[[:space:]]*/,/g'" ",1,2,3,4,5," \
#	"" "12345"

# testing "description" "arguments" "result" "infile" "stdin"

testing "sed n command must reset 'substituted' bit" \
	"sed 's/1/x/;T;n;: next;s/3/y/;t quit;n;b next;: quit;q'" \
	"0\nx\n2\ny\n" "" "0\n1\n2\n3\n"

testing "sed d does not break n,m matching" \
	"sed -n '1d;1,3p'" \
	"second\nthird\n" "" "first\nsecond\nthird\nfourth\n"

testing "sed d does not break n,regex matching" \
	"sed -n '1d;1,/hir/p'" \
	"second\nthird\n" "" "first\nsecond\nthird\nfourth\n"

testing "sed d does not break n,regex matching #2" \
	"sed -n '1,5d;1,/hir/p'" \
	"second2\nthird2\n" "" \
	"first\nsecond\nthird\nfourth\n""first2\nsecond2\nthird2\nfourth2\n"

testing "sed 2d;2,1p (gnu compat)" \
	"sed -n '2d;2,1p'" \
	"third\n" "" \
	"first\nsecond\nthird\nfourth\n"

# Regex means: "match / at BOL or nothing, then one or more not-slashes".
# The bug was that second slash in /usr/lib was treated as "at BOL" too.
testing "sed beginning (^) matches only once" \
	"sed 's,\(^/\|\)[^/][^/]*,>\0<,g'" \
	">/usr</>lib<\n" "" \
	"/usr/lib\n"

exit $FAILCOUNT
1	niro	532	#!/bin/sh
2
3			# SUSv3 compliant sed tests.
4			# Copyright 2005 by Rob Landley <rob@landley.net>
5			# Licensed under GPL v2, see file LICENSE for details.
6
7	niro	984	. ./testing.sh
8	niro	532
9			# testing "description" "arguments" "result" "infile" "stdin"
10
11			# Corner cases
12			testing "sed no files (stdin)" 'sed ""' "hello\n" "" "hello\n"
13			testing "sed explicit stdin" 'sed "" -' "hello\n" "" "hello\n"
14			testing "sed handles empty lines" "sed -e 's/\$/@/'" "@\n" "" "\n"
15			testing "sed stdin twice" 'sed "" - -' "hello" "" "hello"
16
17			# Trailing EOF.
18			# Match $, at end of each file or all files?
19
20			# -e corner cases
21			# without -e
22			# multiple -e
23			# interact with a
24			# -eee arg1 arg2 arg3
25			# -f corner cases
26			# -e -f -e
27			# -n corner cases
28			# no newline at EOF?
29			# -r corner cases
30			# Just make sure it works.
31			# -i corner cases:
32			# sed -i -
33			# permissions
34			# -i on a symlink
35			# on a directory
36			# With $ last-line test
37			# Continue with \
38			# End of script with trailing \
39
40			# command list
41			testing "sed accepts blanks before command" "sed -e '1 d'" "" "" ""
42			testing "sed accepts newlines in -e" "sed -e 'i\
43			1
44			a\
45			3'" "1\n2\n3\n" "" "2\n"
46			testing "sed accepts multiple -e" "sed -e 'i\' -e '1' -e 'a\' -e '3'" \
47			"1\n2\n3\n" "" "2\n"
48
49			# substitutions
50			testing "sed -n" "sed -n -e s/foo/bar/ -e s/bar/baz/" "" "" "foo\n"
51			testing "sed s//p" "sed -e s/foo/bar/p -e s/bar/baz/p" "bar\nbaz\nbaz\n" \
52			"" "foo\n"
53			testing "sed -n s//p" "sed -ne s/abc/def/p" "def\n" "" "abc\n"
54	niro	984	test x"$SKIP_KNOWN_BUGS" = x"" && {
55	niro	532	testing "sed s//g (exhaustive)" "sed -e 's/[[:space:]]*/,/g'" ",1,2,3,4,5,\n" \
56			"" "12345\n"
57	niro	984	}
58	niro	532	testing "sed s arbitrary delimiter" "sed -e 's woo boing '" "boing\n" "" "woo\n"
59			testing "sed s chains" "sed -e s/foo/bar/ -e s/bar/baz/" "baz\n" "" "foo\n"
60			testing "sed s chains2" "sed -e s/foo/bar/ -e s/baz/nee/" "bar\n" "" "foo\n"
61			testing "sed s [delimiter]" "sed -e 's@[@]@@'" "onetwo" "" "one@two"
62	niro	816	testing "sed s with \\t (GNU ext)" "sed 's/\t/ /'" "one two" "" "one\ttwo"
63	niro	532
64			# branch
65			testing "sed b (branch)" "sed -e 'b one;p;: one'" "foo\n" "" "foo\n"
66			testing "sed b (branch with no label jumps to end)" "sed -e 'b;p'" \
67			"foo\n" "" "foo\n"
68
69			# test and branch
70			testing "sed t (test/branch)" "sed -e 's/a/1/;t one;p;: one;p'" \
71			"1\n1\nb\nb\nb\nc\nc\nc\n" "" "a\nb\nc\n"
72			testing "sed t (test/branch clears test bit)" "sed -e 's/a/b/;:loop;t loop'" \
73			"b\nb\nc\n" "" "a\nb\nc\n"
74			testing "sed T (!test/branch)" "sed -e 's/a/1/;T notone;p;: notone;p'" \
75			"1\n1\n1\nb\nb\nc\nc\n" "" "a\nb\nc\n"
76
77	niro	984	test x"$SKIP_KNOWN_BUGS" = x"" && {
78	niro	532	# Normal sed end-of-script doesn't print "c" because n flushed the pattern
79			# space. If n hits EOF, pattern space is empty when script ends.
80			# Query: how does this interact with no newline at EOF?
81			testing "sed n (flushes pattern space, terminates early)" "sed -e 'n;p'" \
82			"a\nb\nb\nc\n" "" "a\nb\nc\n"
83			# N does _not_ flush pattern space, therefore c is still in there @ script end.
84			testing "sed N (doesn't flush pattern space when terminating)" "sed -e 'N;p'" \
85			"a\nb\na\nb\nc\n" "" "a\nb\nc\n"
86	niro	984	}
87	niro	532	testing "sed address match newline" 'sed "/b/N;/b\\nc/i woo"' \
88			"a\nwoo\nb\nc\nd\n" "" "a\nb\nc\nd\n"
89
90			# Multiple lines in pattern space
91			testing "sed N (stops at end of input) and P (prints to first newline only)" \
92			"sed -n 'N;P;p'" "a\na\nb\n" "" "a\nb\nc\n"
93
94			# Hold space
95			testing "sed G (append hold space to pattern space)" 'sed G' "a\n\nb\n\nc\n\n" \
96			"" "a\nb\nc\n"
97			#testing "sed g/G (swap/append hold and patter space)"
98			#testing "sed g (swap hold/pattern space)"
99
100			testing "sed d ends script iteration" \
101			"sed -e '/ook/d;s/ook/ping/p;i woot'" "" "" "ook\n"
102			testing "sed d ends script iteration (2)" \
103			"sed -e '/ook/d;a\' -e 'bang'" "woot\nbang\n" "" "ook\nwoot\n"
104
105			# Multiple files, with varying newlines and NUL bytes
106	niro	984	test x"$SKIP_KNOWN_BUGS" = x"" && {
107	niro	532	testing "sed embedded NUL" "sed -e 's/woo/bang/'" "\0bang\0woo\0" "" \
108			"\0woo\0woo\0"
109	niro	984	}
110	niro	532	testing "sed embedded NUL g" "sed -e 's/woo/bang/g'" "bang\0bang\0" "" \
111			"woo\0woo\0"
112	niro	984	test x"$SKIP_KNOWN_BUGS" = x"" && {
113	niro	532	echo -e "/woo/a he\0llo" > sed.commands
114			testing "sed NUL in command" "sed -f sed.commands" "woo\nhe\0llo\n" "" "woo"
115			rm sed.commands
116	niro	984	}
117	niro	532
118			# sed has funky behavior with newlines at the end of file. Test lots of
119			# corner cases with the optional newline appending behavior.
120
121			testing "sed normal newlines" "sed -e 's/woo/bang/' input -" "bang\nbang\n" \
122			"woo\n" "woo\n"
123			testing "sed leave off trailing newline" "sed -e 's/woo/bang/' input -" \
124			"bang\nbang" "woo\n" "woo"
125			testing "sed autoinsert newline" "sed -e 's/woo/bang/' input -" "bang\nbang" \
126			"woo" "woo"
127			testing "sed empty file plus cat" "sed -e 's/nohit//' input -" "one\ntwo" \
128			"" "one\ntwo"
129			testing "sed cat plus empty file" "sed -e 's/nohit//' input -" "one\ntwo" \
130			"one\ntwo" ""
131	niro	984	test x"$SKIP_KNOWN_BUGS" = x"" && {
132	niro	532	testing "sed append autoinserts newline" "sed -e '/woot/a woo' -" \
133			"woot\nwoo\n" "" "woot"
134	niro	984	}
135	niro	532	testing "sed insert doesn't autoinsert newline" "sed -e '/woot/i woo' -" \
136			"woo\nwoot" "" "woot"
137			testing "sed print autoinsert newlines" "sed -e 'p' -" "one\none" "" "one"
138			testing "sed print autoinsert newlines two files" "sed -e 'p' input -" \
139			"one\none\ntwo\ntwo" "one" "two"
140			testing "sed noprint, no match, no newline" "sed -ne 's/woo/bang/' input" \
141			"" "no\n" ""
142			testing "sed selective matches with one nl" "sed -ne 's/woo/bang/p' input -" \
143			"a bang\nc bang\n" "a woo\nb no" "c woo\nd no"
144			testing "sed selective matches insert newline" \
145			"sed -ne 's/woo/bang/p' input -" "a bang\nb bang\nd bang" \
146			"a woo\nb woo" "c no\nd woo"
147			testing "sed selective matches noinsert newline" \
148			"sed -ne 's/woo/bang/p' input -" "a bang\nb bang" "a woo\nb woo" \
149			"c no\nd no"
150	niro	984	test x"$SKIP_KNOWN_BUGS" = x"" && {
151	niro	532	testing "sed clusternewline" \
152			"sed -e '/one/a 111' -e '/two/i 222' -e p input -" \
153			"one\none\n111\n222\ntwo\ntwo" "one" "two"
154	niro	984	}
155	niro	816	testing "sed subst+write" \
156			"sed -e 's/i/z/' -e 'woutputw' input -; echo -n X; cat outputw" \
157			"thzngy\nagaznXthzngy\nagazn" "thingy" "again"
158			rm outputw
159			testing "sed trailing NUL" \
160			"sed 's/i/z/' input -" \
161			"a\0b\0\nc" "a\0b\0" "c"
162			testing "sed escaped newline in command" \
163			"sed 's/a/z\\
164			z/' input" \
165			"z\nz" "a" ""
166	niro	532
167			# Test end-of-file matching behavior
168
169			testing "sed match EOF" "sed -e '"'$p'"'" "hello\nthere\nthere" "" \
170			"hello\nthere"
171			testing "sed match EOF two files" "sed -e '"'$p'"' input -" \
172			"one\ntwo\nthree\nfour\nfour" "one\ntwo" "three\nfour"
173	niro	816	# sed match EOF inline: gnu sed 4.1.5 outputs this:
174			#00000000 6f 6e 65 0a 6f 6f 6b 0a 6f 6f 6b 0a 74 77 6f 0a \|one.ook.ook.two.\|
175			#00000010 0a 74 68 72 65 65 0a 6f 6f 6b 0a 6f 6f 6b 0a 66 \|.three.ook.ook.f\|
176			#00000020 6f 75 72 \|our\|
177			# which looks buggy to me.
178			$ECHO -ne "three\nfour" > input2
179	niro	532	testing "sed match EOF inline" \
180			"sed -e '"'$i ook'"' -i input input2 && cat input input2" \
181			"one\nook\ntwothree\nook\nfour" "one\ntwo" ""
182			rm input2
183
184			# Test lie-to-autoconf
185
186			testing "sed lie-to-autoconf" "sed --version \| grep -o 'GNU sed version '" \
187			"GNU sed version \n" "" ""
188
189			# Jump to nonexistent label
190	niro	984	test x"$SKIP_KNOWN_BUGS" = x"" && {
191			# Incompatibility: illegal jump is not detected if input is ""
192			# (that is, no lines at all). GNU sed 4.1.5 complains even in this case
193			testing "sed nonexistent label" "sed -e 'b walrus' 2>/dev/null \|\| echo yes" \
194	niro	532	"yes\n" "" ""
195	niro	984	}
196	niro	532
197			testing "sed backref from empty s uses range regex" \
198			"sed -e '/woot/s//eep \0 eep/'" "eep woot eep" "" "woot"
199
200			testing "sed backref from empty s uses range regex with newline" \
201			"sed -e '/woot/s//eep \0 eep/'" "eep woot eep\n" "" "woot\n"
202
203			# -i with no filename
204
205			touch ./- # Detect gnu failure mode here.
206			testing "sed -i with no arg [GNUFAIL]" "sed -e '' -i 2> /dev/null \|\| echo yes" \
207			"yes\n" "" ""
208			rm ./- # Clean up
209
210			testing "sed s/xxx/[/" "sed -e 's/xxx/[/'" "[\n" "" "xxx\n"
211
212			# Ponder this a bit more, why "woo not found" from gnu version?
213			#testing "sed doesn't substitute in deleted line" \
214			# "sed -e '/ook/d;s/ook//;t woo;a bang;'" "bang" "" "ook\n"
215
216			# This makes both seds very unhappy. Why?
217			#testing "sed -g (exhaustive)" "sed -e 's/[[:space:]]*/,/g'" ",1,2,3,4,5," \
218			# "" "12345"
219
220	niro	816	# testing "description" "arguments" "result" "infile" "stdin"
221
222			testing "sed n command must reset 'substituted' bit" \
223			"sed 's/1/x/;T;n;: next;s/3/y/;t quit;n;b next;: quit;q'" \
224			"0\nx\n2\ny\n" "" "0\n1\n2\n3\n"
225
226	niro	984	testing "sed d does not break n,m matching" \
227			"sed -n '1d;1,3p'" \
228			"second\nthird\n" "" "first\nsecond\nthird\nfourth\n"
229
230			testing "sed d does not break n,regex matching" \
231			"sed -n '1d;1,/hir/p'" \
232			"second\nthird\n" "" "first\nsecond\nthird\nfourth\n"
233
234			testing "sed d does not break n,regex matching #2" \
235			"sed -n '1,5d;1,/hir/p'" \
236			"second2\nthird2\n" "" \
237			"first\nsecond\nthird\nfourth\n""first2\nsecond2\nthird2\nfourth2\n"
238
239			testing "sed 2d;2,1p (gnu compat)" \
240			"sed -n '2d;2,1p'" \
241			"third\n" "" \
242			"first\nsecond\nthird\nfourth\n"
243
244			# Regex means: "match / at BOL or nothing, then one or more not-slashes".
245			# The bug was that second slash in /usr/lib was treated as "at BOL" too.
246			testing "sed beginning (^) matches only once" \
247			"sed 's,\(^/\\|\)[^/][^/]*,>\0<,g'" \
248			">/usr</>lib<\n" "" \
249			"/usr/lib\n"
250
251	niro	532	exit $FAILCOUNT