From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <138575260906260454k2865f408t7e438cc8b8e9bb11@mail.gmail.com> References: <138575260906260250hca23acbi34aed21566004bad@mail.gmail.com> <138575260906260454k2865f408t7e438cc8b8e9bb11@mail.gmail.com> Date: Fri, 26 Jun 2009 14:05:31 +0200 Message-ID: From: Rudolf Sykora To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] Sam commands in acme Topicbox-Message-UUID: 0f7669e2-ead5-11e9-9d60-3106f5b1d025 2009/6/26 hugo rivera : > 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 =A0mark 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