From: David Presotto <presotto@closedmind.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] sam -d reading from stdin?
Date: Sat, 31 Jan 2004 08:07:00 -0500 [thread overview]
Message-ID: <ba2867fcec3aac18921818dd4220b01e@plan9.bell-labs.com> (raw)
In-Reply-To: <7fe6ba52bb6362ece115dcddac6eab0b@mteege.de>
How about
tee /fd/2 |[2] {tr A-Z a-z | sed -n 's/^reply-to: *//p
/^$/q'} >/env/x
Well, its a temp file but just the environmnt one you had anyways. You can't use
$x later in the script because the shell won't have noticed that you changed an
env variable...
The /^$/q just gets you out when the message starts so you don't snarf any body
messages
next prev parent reply other threads:[~2004-01-31 13:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-31 12:40 Matthias Teege
2004-01-31 13:07 ` David Presotto [this message]
2004-02-01 0:18 ` Geoff Collyer
2004-02-01 0:30 ` Geoff Collyer
2004-02-01 3:31 ` boyd, rounin
2004-02-01 13:51 ` Matthias Teege
2004-02-01 14:03 ` boyd, rounin
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=ba2867fcec3aac18921818dd4220b01e@plan9.bell-labs.com \
--to=presotto@closedmind.org \
--cc=9fans@cse.psu.edu \
/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).