From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <df49a7370807170701x4071d3b2ga93321342c8a9a1e@mail.gmail.com>
Date: Thu, 17 Jul 2008 15:01:41 +0100
From: "roger peppe" <rogpeppe@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
In-Reply-To: <F683F1B8-6821-4227-A06D-069CDBDC3434@mac.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <df49a7370807170303t38cfd85euf8e85d7ff85de32c@mail.gmail.com>
	<F683F1B8-6821-4227-A06D-069CDBDC3434@mac.com>
Subject: Re: [9fans] acme g/$/ funny
Topicbox-Message-UUID: ea899c04-ead3-11e9-9d60-3106f5b1d025

On Thu, Jul 17, 2008 at 2:07 PM, Pietro Gagliardi <pietro10@mac.com> wrote:
> ,x/$/a/foo/

i was actually trying to do something slightly different;
my original command was:

  ,x/^[ \t]*let.*/v/in$/a/ in/

and i worked around it by doing

  ,x/^[ \t]let.*\n/v/in\n/x/\n/i/ in/

which wasn't too bad. i just wondered
if the behaviour i saw was actually a bug,
as $ matches the null string at the end of a line,
and i was matching against the null string at the end
of a line. i think i understand why it doesn't work;
but should it work differently?