From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <881ffd69444ad67e5460b67e49092763@krabbe.dyndns.org>
To: <9fans@9fans.net>
Date: Wed, 12 Aug 2015 09:48:39 +0200
From: Ingo Krabbe <ikrabbe.ask@gmail.com>
In-Reply-To: <CAOEdRO1rM0TgDT16Q=2dEf_7Ksyrt4aSzZxqQ2cw5m89Hk7hiQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] p9p sed vs linux sed
Topicbox-Message-UUID: 65e4a3ee-ead9-11e9-9d60-3106f5b1d025

You mean perseus=; is your prompt? Strange.

Actually sed is a line based command and should add a newline, imho. You can simply use tr -d '\n'.

There are several quoting differences between plan9 sed and linux sed and I think the \+ operator doesn't work anyway in linux sed, but I might be wrong with this statement.

cheers,
ingo

> Hello,
>
> is this as expected?
>
> perseus=; echo -n aaa | 9 sed 's/^/</' |tr -d '\n'
> <aaa
> perseus=; echo -n aaa | sed 's/^/</'
> <aaaperseus=;
>
>
> For me the linux sed does what I expect,
> but not the p9p one (it adds a newline). Why?
>
> Thanks!
> Ruda