From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <52727C23.8070302@gmx.de> Date: Thu, 31 Oct 2013 16:49:55 +0100 From: Friedrich Psiorz User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> References: <526FE8DB.5040709@gmx.de> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [9fans] acme/sam language question Topicbox-Message-UUID: 891f074c-ead8-11e9-9d60-3106f5b1d025 It works for me, but I found another inconsistency. I tried it on p9p and 9vx, both in acme and sam. 9vx acme is different form the others, for some reason. It does print the string between A and B, but prints it with CC and not with DD like sam and like p9p acme. ~Fritz Am 31.10.2013 16:21, schrieb Rudolf Sykora: > On 30 October 2013 08:47, Rudolf Sykora wrote: >> On 29 October 2013 17:56, Friedrich Psiorz wrote: >>> this should do the trick >>> >>> /A/+#0;/B/-#0 >>> g/CC/ s/CC/DD/g >>> p >> >> Thanks for the suggestion, the g construct didn't come to my mind. >> However, it doesn't work for me: again, if CC is there, it works; >> if it's not, then the final dot only contains the match for the /A/ instead >> of the whole stretch from A to B. >> >> Ruda > > no other suggestions? > Thanks > Ruda >