Re: [9front] sed bug?

[Eckard Brauer <eckard.brauer@gmx.de>]

[-- Attachment #1: Type: text/plain, Size: 1199 bytes --]

At least it look inconsistent:

% {echo test; echo test1; echo test2;echo test3} | sed '1,/^test$/d'
% {echo test; echo test1; echo test2;echo test3} | sed '1,/^test1$/d'
test2
test3
% {echo test; echo test1; echo test2;echo test3} | sed '1,/^test2$/d'
test3

seems search starts just after addressed line (1 in this case): in fist
case nothing is found, so search goes until end, then mothing remains
for output.

as the man page states:

	[address [, address] ] function [argument ...]

as valid, "1/test$/d' should work, but it seems not to be the case:

% {echo test; echo test1; echo test2;echo test3} | sed '1/^test$/d'
sed: Unrecognized command: 1/^test$/d

BTW, GNU sed (Linux) seems to behave similar.

Am Tue, 13 Nov 2018 13:04:01 -0700
schrieb Joe M <joe9mail@gmail.com>:

> Hello,
> 
> umbraticus@prosimetrum.com wrote:
>  [...]  
>  [...]  
> 
> yes, my bad. I pasted the wrong command. It should be a 1 instead of
> 0.
> 
>  [...]  
>  [...]  
>  [...]  
> 
> I stumbled upon the same workaround too. On a similar note, this
> command works fine also:
> 
> {echo test; echo test1; echo test2} | sed '1,1d'
> 
> Thanks again



-- 
:)

[-- Attachment #2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 195 bytes --]