From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from asquith.prosimetrum.com ([125.236.209.157]) by ewsd; Tue Nov 13 14:30:36 EST 2018
Message-ID: <AB197762BC3998A98109E128E8622B00@prosimetrum.com>
Date: Wed, 14 Nov 2018 08:32:43 +1300
From: umbraticus@prosimetrum.com
To: 9front@9front.org
Subject: Re: [9front] sed bug?
In-Reply-To: 20181113170851.GA5870@master
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: compliant responsive hosting-based cache hosting-oriented generator 

> This works fine, it outputs test2
> {echo test; echo test1; echo test2} | sed '0,/^test1$/d'

really? I get: sed: line number 0 is illegal

for this one: 

>{echo test; echo test1; echo test2} | sed '1,/^test$/d' # has no output

it deletes line 1, then continues deleting lines until it finds ^test$
which it never does. Perhaps adding a newline at the start is the quickest
way to get what you want?

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

test1
test2

umbraticus