From: "boyd, rounin" <boyd@insultant.net>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] fscons bug
Date: Thu, 24 Jun 2004 20:55:42 +0200 [thread overview]
Message-ID: <070f01c45a1c$db4a4bc0$08fa7d50@SOMA> (raw)
In-Reply-To: <71c3fdee35f530673fe504e36d037dfc@davidashen.net>
> >> cpu% con -l /srv/fscons << EOF
> >
> > how is con supposed to know that it should wait for some output
> > from the transaction?
>
> OK. I don't understand something basic.
yeah, con exits when reading fd 0 returns EOF, which will be
pretty ricky-tick on a here document.
RTFS
prev parent reply other threads:[~2004-06-24 18:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-24 17:35 dvd
2004-06-24 17:53 ` rog
2004-06-24 18:04 ` Charles Forsyth
2004-06-24 18:17 ` rog
2004-06-24 18:14 ` Charles Forsyth
2004-06-24 18:23 ` rog
2004-06-25 21:00 ` Scott Schwartz
2004-06-24 18:37 ` dvd
2004-06-24 18:49 ` rog
2004-06-24 18:55 ` boyd, rounin [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='070f01c45a1c$db4a4bc0$08fa7d50@SOMA' \
--to=boyd@insultant.net \
--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).