From: rog@vitanuova.com
To: russcox@gmail.com, 9fans@cse.psu.edu
Subject: Re: [9fans] tip'o'day -- hack
Date: Fri, 22 Apr 2005 00:16:20 +0100 [thread overview]
Message-ID: <e3ee47ddf04e933a8ba09d415a81a936@vitanuova.com> (raw)
In-Reply-To: <ee9e417a050421160811a173db@mail.gmail.com>
> you're supposed to use rx for this.
>
> echo hello | rx wc | tr '0-9'
>
> cpu is for interactive sessions, hence the /dev/cons.
it's true that rx does this (and without the 9p overhead too), but you
don't get /mnt/term with rx, and that's sometimes crucial.
prev parent reply other threads:[~2005-04-21 23:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-21 22:42 Tim Newsham
2005-04-21 23:03 ` David Leimbach
2005-04-21 23:07 ` rog
2005-04-21 23:08 ` Russ Cox
2005-04-21 23:16 ` rog [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=e3ee47ddf04e933a8ba09d415a81a936@vitanuova.com \
--to=rog@vitanuova.com \
--cc=9fans@cse.psu.edu \
--cc=russcox@gmail.com \
/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).