From: culliton@srg.af.mil (Tom Culliton x2278)
To: arnold@cc.gatech.edu, culliton@srg.srg.af.mil,
rc@hawkwind.utcs.toronto.edu, vons@cesar.crbca1.sinet.slb.com
Subject: Re: A patch to add builtin read (small bug)
Date: Thu, 23 Sep 1993 14:10:08 -0400 [thread overview]
Message-ID: <9309231410.aa05022@ceres.srg.af.mil> (raw)
<Arnold suggests>
> Doesn't rc fork builtins when they're redirected? This may be why
> redirections on read didn't show up in /bin/sh until System III or
> System V.
That sounds like the right answer to me and since no other builtin
command takes input... Sigh... This is looking like a bigger job than
expected. If it's not obvious how to fix this I may withdraw the read
patch until someone can do it right.
Tom
next reply other threads:[~1993-09-23 22:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-09-23 18:10 Tom Culliton x2278 [this message]
-- strict thread matches above, loose matches on Subject: below --
1993-09-23 16:03 gjv%atlas%cesar
1993-09-23 15:36 Arnold Robbins
1993-09-23 15:19 Tom Culliton x2278
1993-09-23 7:30 gjv%atlas%cesar
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=9309231410.aa05022@ceres.srg.af.mil \
--to=culliton@srg.af.mil \
--cc=arnold@cc.gatech.edu \
--cc=culliton@srg.srg.af.mil \
--cc=rc@hawkwind.utcs.toronto.edu \
--cc=vons@cesar.crbca1.sinet.slb.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).