From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <52727C23.8070302@gmx.de>
References: <CAOEdRO1XQmHP0DpMKK_t6svkdwY=3pnX-bmsJc6Uk1eKxzW+yg@mail.gmail.com>
	<526FE8DB.5040709@gmx.de>
	<CAOEdRO1m07V9jAXiYt62JdLHVaKd+D-yQ7jKRpQRtz0bxaRXcQ@mail.gmail.com>
	<CAOEdRO15fHkiXH0Hy3CmYZ1vbO4-pLwa4OwG5P_w8+o4Uv7v5Q@mail.gmail.com>
	<52727C23.8070302@gmx.de>
Date: Thu, 31 Oct 2013 20:24:59 +0100
Message-ID: <CAOEdRO1LH4cX7n_TFRFkN3na2wsnoOoiqEtFR-51TpZO4Af_Jg@mail.gmail.com>
From: Rudolf Sykora <rudolf.sykora@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [9fans] acme/sam language question
Topicbox-Message-UUID: 8924bf2a-ead8-11e9-9d60-3106f5b1d025

On 31 October 2013 16:49, Friedrich Psiorz <f.psiorz@gmx.de> wrote:
> It works for me, but I found another inconsistency.
>
> I tried it on p9p and 9vx, both in acme and sam.

>>>> /A/+#0;/B/-#0
>>>> g/CC/ s/CC/DD/g
>>>> p

Well. If I use these commands one by one inside p9p acme
(and probably sam, too), I truly get what I want (and what
you say). The problem appears when I want to run it from
a script like this:

sam -d <<EOF $1  >[2] /dev/null
/A/+#0;/B/-#0
g/CC/ s/CC/DD/g
p
EOF

then you get, since the g is on a seperate line, an extra
output from the line before g. And if you try to join g with
the match like

sam -d <<EOF $1  >[2] /dev/null
/A/+#0;/B/-#0 g/CC/ s/CC/DD/g
p
EOF

then you get no output if CC is not between A and B
(although when it is there, you get what I want).
In neither case I am fully satisfied. :)

Thanks
Ruda