From: dexen deVries <dexen.devries@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] acme + plumber question
Date: Fri, 5 Oct 2012 14:31:06 +0200 [thread overview]
Message-ID: <4926154.4vdIdx5h1u@coil> (raw)
In-Reply-To: <16bd8e79d5711d8f2f25bfa541305f61@brasstown.quanstro.net>
On Friday 05 of October 2012 07:49:57 erik quanstrom wrote:
> > certain program† i run in acme produces error messages in form ``$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 having
> > to
> > perform full mouse sweep :D
> >
> > the question: is there a sensible way to access text /around/ text plumbed
> > from acme (i.e., context), either from plumber rules or from plumber
> > client
> > program?
>
> 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 double-
click on line edge), it doesn't seem to work with the plumber. either is not
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 plumber
treats LF character specially?
($TEST_SCRIPT is a small helper to test whether the rule matched)
fwiw, that's p9p acme and plumber.
--
dexen deVries
[[[↓][→]]]
next prev parent reply other threads:[~2012-10-05 12:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-05 10:23 dexen deVries
2012-10-05 11:49 ` erik quanstrom
2012-10-05 12:31 ` dexen deVries [this message]
2012-10-05 12:44 ` dexen deVries
2012-10-05 13:04 ` erik quanstrom
2012-10-05 13:08 ` dexen deVries
2012-10-05 14:25 ` erik quanstrom
2012-10-05 14:34 ` erik quanstrom
2012-10-05 14:48 ` dexen deVries
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4926154.4vdIdx5h1u@coil \
--to=dexen.devries@gmail.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).