From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <8533-1383720139-778543@sneakemail.com> From: =?ISO-8859-1?Q?Rub=E9n_Berenguel?= Date: Wed, 6 Nov 2013 14:06:25 +0100 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=047d7b2ee18b3c42cd04ea81d2f7 Subject: Re: [9fans] Help with plumbing rules Topicbox-Message-UUID: 89dab0a0-ead8-11e9-9d60-3106f5b1d025 --047d7b2ee18b3c42cd04ea81d2f7 Content-Type: text/plain; charset=ISO-8859-1 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, it just takes a while to figure out how to mix all the pieces. Ruben On Wed, Nov 6, 2013 at 2:02 PM, Mark van Atten wrote: > > 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 profile to put its > messages in the right form: > > # for lacheck: format output for acme > fn lacheck $* {builtin lacheck $* | 9 sed 's/"(.*)".*line ([0-9]+): > (.*)/\1:\2:\3/'} > > Can you do something similar? > > Mark. > > --047d7b2ee18b3c42cd04ea81d2f7 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Tooting my own horn: I explained a few examples of plumbin= g rules in this post of mine (I posted it on reddit/r/plan9 a while ago)

In the end, everything is written down in the var= ious man pages describing plumb and plumber, it just takes a while to figur= e out how to mix all the pieces.

Ruben


On Wed, Nov 6= , 2013 at 2:02 PM, Mark van Atten <vanattenmark@gmail.com> wrote:
> PS: Once I get this w= orking I'll tackle the diagnostic messages I get when
> compiling Java code using maven (not my choice). =A0They look like
> [error] /home/pcanning/src/java/test/PerfTest.java:[66,1] error: reach= ed end
> of file while parsing

For lacheck, a Latex checker, I have this in my profile to put its messages in the right form:

# for lacheck: format output for acme
fn lacheck $* {builtin lacheck $* | 9 sed 's/"(.*)".*line ([0= -9]+):
(.*)/\1:\2:\3/'}

Can you do something similar?

Mark.


--047d7b2ee18b3c42cd04ea81d2f7--