From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
Date: Fri,  5 Oct 2012 09:04:55 -0400
To: 9fans@9fans.net
Message-ID: <c93703a07e40452787147e62b3525945@brasstown.quanstro.net>
In-Reply-To: <12158316.NY6jp8kkEc@coil>
References: <1492275.224dsYbtlA@coil>
	<16bd8e79d5711d8f2f25bfa541305f61@brasstown.quanstro.net>
	<12158316.NY6jp8kkEc@coil>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [9fans] acme + plumber question
Topicbox-Message-UUID: bd37628c-ead7-11e9-9d60-3106f5b1d025

On Fri Oct  5 08:45:47 EDT 2012, dexen.devries@gmail.com wrote:
> On Friday 05 of October 2012 07:49:57 erik quanstrom wrote:
> > does it not work to write a plumb rule that parses the whole line?   =
then
> > it would possible to double-click at the edges of the line to select =
the
> > whole line.
>=20
> ok, got it working. the important bit is regcompnl() vs. regcomp().
>=20
>=20
> simple problems are simple:
>=20
> $PLAN9/src/cmd/plumb $ 9 diff -c -n rules.c-orig rules.c
> X-rules.c:363 c rules.c:363
> <                       r->regex =3D regcomp(r->qarg);
> ---                                                                    =
                                                                         =
                                          =20
> >                       r->regex =3D regcompnl(r->qarg);               =
                                                                         =
          =20

you'll probablly rather put a literal newline in your rule.
you probablly don't want any surprises in other rules that
expect . not to match \n.  =E2=98=BA

- erik