9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: hugo rivera <uair00@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Sam commands in acme
Date: Fri, 26 Jun 2009 14:21:52 +0200	[thread overview]
Message-ID: <138575260906260521g542ebd04wfe5de4b1e29af9b@mail.gmail.com> (raw)
In-Reply-To: <a560a5d00906260505n7eec7c5fxba12f9640844a7e9@mail.gmail.com>

Yes, you are right. Now I understand it, I missed the / after \*, so I
was thinking that the comma was inside the regexp.
Thanks a lot :-)

2009/6/26 Rudolf Sykora <rudolf.sykora@gmail.com>:
> 2009/6/26 hugo rivera <uair00@gmail.com>:
>> I tested the command you suggested (,x/\/\*/.,/\*\//) and it works as
>> I wanted, thanks. But there's something I still don't understand and
>> is the meaning of that comma in there. As far as I know, the comma is
>> a  mark that delimits the addresses that acme understands, but I do
>> not know how a comma is interpreted inside a regexp. I'd really
>> appreciate if you could clarify this matter to me.
>
> I think, the comma is not in a regexp. The 'x' command syntax is
> x/regexp/command
> and the comma is a part of the command: choose the area from the dot
> (included) to the '*/'
>
> Ruda
>
>



--
Hugo



  reply	other threads:[~2009-06-26 12:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-26  9:50 hugo rivera
2009-06-26 10:42 ` yy
2009-06-26 11:54   ` hugo rivera
2009-06-26 12:05     ` Rudolf Sykora
2009-06-26 12:21       ` hugo rivera [this message]
2009-06-26 10:57 ` roger peppe
2009-06-27 18:17   ` J.R. Mauro
2009-06-27 19:20     ` Rob Pike
2009-06-27 20:32       ` J.R. Mauro
2009-06-29 17:03       ` roger peppe
2009-06-29 17:20         ` erik quanstrom

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=138575260906260521g542ebd04wfe5de4b1e29af9b@mail.gmail.com \
    --to=uair00@gmail.com \
    --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).