From: matt <maht-9fans@maht0x0r.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] handling output
Date: Thu, 1 Oct 2009 10:29:51 +0100 [thread overview]
Message-ID: <4AC4768F.7000300@maht0x0r.net> (raw)
In-Reply-To: <138575260910010209n6f02c9aaqae533c2fb5402746@mail.gmail.com>
Tee part of the POSIX standard
http://www.opengroup.org/onlinepubs/9699919799/utilities/tee.html
hugo rivera wrote:
>Great, thanks.
>Looks like plan 9 guys have thought about everything useful ☺ (and
>that I didn't do my homework).
>
>2009/10/1, roger peppe <rogpeppe@gmail.com>:
>
>
>>2009/10/1 hugo rivera <uair00@gmail.com>:
>>
>>
>>
>>>I've been wondering for a while if there's some way to multiplex (if
>>>
>>>
>> > this is the correct term) stdout for a given program:
>>
>>
>>that's what tee does.
>>
>> e.g.
>> ls | tee >{grep regexp1 > file1} >{grep regexp2 > file2}
>>
>>
>>
>>
>
>
>
>
next prev parent reply other threads:[~2009-10-01 9:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-01 8:26 hugo rivera
2009-10-01 8:38 ` roger peppe
2009-10-01 9:09 ` hugo rivera
2009-10-01 9:29 ` matt [this message]
2009-10-01 9:52 ` hugo rivera
2009-10-01 8:44 ` Sam Watkins
2009-10-01 8:45 ` Richard Miller
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=4AC4768F.7000300@maht0x0r.net \
--to=maht-9fans@maht0x0r.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).