From mboxrd@z Thu Jan  1 00:00:00 1970
From: dexen deVries <dexen.devries@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Date: Fri,  5 Oct 2012 15:08:38 +0200
Message-ID: <5945870.BeEu8mdyey@coil>
User-Agent: KMail/4.9.2 (Linux/3.6.0-l46; KDE/4.9.2; x86_64; ; )
In-Reply-To: <c93703a07e40452787147e62b3525945@brasstown.quanstro.net>
References: <1492275.224dsYbtlA@coil> <12158316.NY6jp8kkEc@coil>
	<c93703a07e40452787147e62b3525945@brasstown.quanstro.net>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"
Subject: Re: [9fans] acme + plumber question
Topicbox-Message-UUID: bd3d992c-ead7-11e9-9d60-3106f5b1d025

On Friday 05 of October 2012 09:04:55 erik quanstrom wrote:
> > $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

good point.


i've tried in two ways, both failed: data matches=3D'foo
' (literal newline) and data matches=3D'foo\n' (C-style escape sequence=
). first=20
trips plumber's parser, the other doesn't match anything -- perhaps \n =
is=20
taken literaly.


--=20
Mateusz Jan Przybylski,