From: Stephen Harris <sharris@nctr.fda.gov>
To: 9fans@cse.psu.edu
Subject: [9fans] pipefile with regular file
Date: Tue, 1 Aug 2000 09:30:55 -0500 [thread overview]
Message-ID: <Pine.LNX.4.10.10008010842590.20863-100000@sch1.NCTR.FDA.GOV> (raw)
Pipefile is great, it's simple and I like how it uses namespace ability
of Plan9 to give us a read "stream filter" which later apps don't need
to even know about.
But I am having a problem with reads on a filtered regular file not ever
hitting EOF:
(this is from memory:)
pipefile -r 'tr a-z A-Z' myfile
cat myfile
(uppercase text to the terminal, but no prompt)
I had to kill the cat with <del> :-o
Same thing if I redirect the cat to a file, have to kill it with <del>.
I thought it would go like:
i ) tr eventually hits EOF
ii) tr exits as last writer on internal pipe (data1) supplying
data to be read by clients (cat) reading myfile
iii) cat reads the remaining data if any and then hits EOF (there
being no more writers), and exits.
Anybody see why that's not happening, or does it work for you?
Steve
Everything you do from now on will be more fun - Windows 95 installation
next reply other threads:[~2000-08-01 14:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-01 14:30 Stephen Harris [this message]
2000-08-02 2:29 rob pike
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=Pine.LNX.4.10.10008010842590.20863-100000@sch1.NCTR.FDA.GOV \
--to=sharris@nctr.fda.gov \
--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).