Tooting my own horn: I explained a few examples of plumbing rules in this
post of mine (I posted it on reddit/r/plan9 a while ago)
http://www.mostlymaths.net/2013/04/just-as-mario-using-plan9-plumber.html
In the end, everything is written down in the various man pages describing
plumb and plumber
> PS: Once I get this working I'll tackle the diagnostic messages I get when
> compiling Java code using maven (not my choice). They look like
> [error] /home/pcanning/src/java/test/PerfTest.java:[66,1] error: reached end
> of file while parsing
For lacheck, a Latex checker, I have this in my pro
Hi,
Question 1:
a flag '-d' can be useful a bit.
Question 2:
$file is filled when you check "arg isfile $1"
Question 3:
I think, the problem is you have to match exact full string is sent to
plumber.
This variant is working:
type is text
data matches 'File "([.a-zA-Z¡-ï¿¿0-9_/\-]*[a-zA-Z¡-ï¿
The diagnostic on the last line should be:
Unexpected End of File at EOF
That's the memorable diagnostic from a CDC compiler.
brucee
On 6 November 2013 17:42, <6o205z...@sneakemail.com> wrote:
> I'm trying to create a plumbing rule so that I can right-click (in acme)
> on the diagnostic messa
I'm trying to create a plumbing rule so that I can right-click (in acme)
on the diagnostic messages produced by Python and get the file opened
with the appropriate line select. Unfortunately my attempts so far have
failed.
Question 1: Is there an easy way to "debug" plumbing rules (I'm using
