rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: Arnold Robbins <arnold@cc.gatech.edu>
To: culliton@srg.srg.af.mil (Tom Culliton x2278),
	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 11:36:13 -0400	[thread overview]
Message-ID: <199309231536.AA02323@penfold.cc.gatech.edu> (raw)
In-Reply-To: Tom Culliton x2278's 78-line message on Sep 23, 11:19am

> Doing:
> 	read x </etc/passwd
> doesn't work either, but my brain isn't working well emough at the
> moment to figure out why.  Anybody got a clue?

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.

(One of the sh man pages from ~ 5.0 says something like "redirections on
read are *now* allowed" - emphasis mine.)


             reply	other threads:[~1993-09-23 15:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1993-09-23 15:36 Arnold Robbins [this message]
  -- strict thread matches above, loose matches on Subject: below --
1993-09-23 18:10 Tom Culliton x2278
1993-09-23 16:03 gjv%atlas%cesar
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=199309231536.AA02323@penfold.cc.gatech.edu \
    --to=arnold@cc.gatech.edu \
    --cc=culliton@srg.srg.af.mil \
    --cc=rc@hawkwind.utcs.toronto.edu \
    --cc=vons@cesar.crbca1.sinet.slb.com \


* 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).