From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [192.168.2.90] ([108.95.88.138]) by ewsd; Fri Jan 11 10:01:22 EST 2019 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (1.0) Subject: Re: [9front] bug in sed From: Stanley Lieber X-Mailer: iPhone Mail (16C101) In-Reply-To: Date: Fri, 11 Jan 2019 10:01:20 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: <0CABEB5C-713C-4FCB-8549-09465977DE96@stanleylieber.com> References: <1547204116.2619408.1631744520.03A21CEC@webmail.messagingengine.com> To: 9front@9front.org List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: lossless agile factory-scale HTTP polling browser shader On Jan 11, 2019, at 7:39 AM, hiro <23hiro@gmail.com> wrote: >=20 > here's another testcase without needing spaces >=20 > cpu% cat > test > asdfasdf > xasdf > cpu% sed 's/^asdf//g' test >=20 > xasdf > cpu% ssam 's/^asdf//g' test > asdf > xasdf isn=E2=80=99t the difference because sed operates line by line, while sam op= erates on the dot? if i understand correctly, you need ,s instead of s at the beginning of the s= am command to apply the transform across the entire input. can=E2=80=99t test now. sl