From: "Rubén Berenguel" <ruben@mostlymaths.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Help with plumbing rules
Date: Wed, 6 Nov 2013 14:06:25 +0100 [thread overview]
Message-ID: <CAHk2O6ovRxhMD-CCKZ2EpG9pHTfBk89MO=FBZeFgiP-bwXHeuQ@mail.gmail.com> (raw)
In-Reply-To: <CALAsyW0rOrXkBswWbXuAHzSUEhcNa5-61u9+QsyUFYHjzCJZJA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1024 bytes --]
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 <vanattenmark@gmail.com>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.
>
>
[-- Attachment #2: Type: text/html, Size: 1628 bytes --]
prev parent reply other threads:[~2013-11-06 13:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-06 6:42 6o205zd02
2013-11-06 6:56 ` Bruce Ellis
2013-11-06 11:08 ` Alexander Sychev
2013-11-06 13:02 ` Mark van Atten
2013-11-06 13:06 ` Rubén Berenguel [this message]
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='CAHk2O6ovRxhMD-CCKZ2EpG9pHTfBk89MO=FBZeFgiP-bwXHeuQ@mail.gmail.com' \
--to=ruben@mostlymaths.net \
--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).