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 14:31:06 +0200
Message-ID: <4926154.4vdIdx5h1u@coil>
User-Agent: KMail/4.9.2 (Linux/3.6.0-l46; KDE/4.9.2; x86_64; ; )
In-Reply-To: <16bd8e79d5711d8f2f25bfa541305f61@brasstown.quanstro.net>
References: <1492275.224dsYbtlA@coil>
	<16bd8e79d5711d8f2f25bfa541305f61@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: bc776ac2-ead7-11e9-9d60-3106f5b1d025

On Friday 05 of October 2012 07:49:57 erik quanstrom wrote:
> > certain program=E2=80=A0 i run in acme produces error messages in f=
orm ``$ERROR in
> > $FILE on line $LINENO''. i have a plumber rule that opens $FILE in =
the
> > acme
> > window, but i'd like it to also position at line $LINENO. without h=
aving
> > to
> > perform full mouse sweep :D
> >=20
> > the question: is there a sensible way to access text /around/ text =
plumbed
> > from acme (i.e., context), either from plumber rules or from plumbe=
r
> > client
> > program?
>=20
> 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.

that would do the trick indeed, except when i select whole line (by dou=
ble-
click on line edge), it doesn't seem to work with the plumber. either i=
s not=20
sent by acme, or it doesn't get matched by the simplest possible rule:

data matches '.*error.*'
type is text
plumb start $TEST_SCRIPT $0

which works a-ok when i manually select text on the line. perhaps plumb=
er=20
treats LF character specially?

($TEST_SCRIPT is a small helper to test whether the rule matched)


fwiw, that's p9p acme and plumber.


--=20
dexen deVries

[[[=E2=86=93][=E2=86=92]]]