9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Friedrich Psiorz <f.psiorz@gmx.de>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] acme/sam language question
Date: Thu, 31 Oct 2013 16:49:55 +0100	[thread overview]
Message-ID: <52727C23.8070302@gmx.de> (raw)
In-Reply-To: <CAOEdRO15fHkiXH0Hy3CmYZ1vbO4-pLwa4OwG5P_w8+o4Uv7v5Q@mail.gmail.com>

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 <rudolf.sykora@gmail.com> wrote:
>> On 29 October 2013 17:56, Friedrich Psiorz <f.psiorz@gmx.de> 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
>




  reply	other threads:[~2013-10-31 15:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-29 15:31 Rudolf Sykora
2013-10-29 16:56 ` Friedrich Psiorz
2013-10-30  7:47   ` Rudolf Sykora
2013-10-31 15:21     ` Rudolf Sykora
2013-10-31 15:49       ` Friedrich Psiorz [this message]
2013-10-31 19:24         ` Rudolf Sykora
2013-11-06 18:47           ` Rudolf Sykora
2013-11-06 20:26             ` Micah Stetson
2013-11-06 20:42             ` Mark van Atten
2013-11-21 13:28               ` Rudolf Sykora
2013-11-21 14:52                 ` Mark van Atten

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52727C23.8070302@gmx.de \
    --to=f.psiorz@gmx.de \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).