rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: haahr@mv.us.adobe.com (Paul Haahr)
To: alan@oldp.astro.wisc.edu
Cc: rc@hawkwind.utcs.toronto.edu
Subject: Re:  redirection and built-ins
Date: Sat, 5 Jun 1993 14:45:04 -0400	[thread overview]
Message-ID: <9306051845.AA04299@astro.mv.us.adobe.com> (raw)

> At the moment,
> 	echo bar | read foo
> is a widely known failing of sh, but with these two changes it would
> work in rc.

the issue is not bindings of pipes, but when pipe forks.  in rc and es,
(though, i've heard, not in Tom Duff's rc) all components of pipelines
are run in child processes.  this is, imho, the cleanest model.  i would
be very upset to see it change.

paul


             reply	other threads:[~1993-06-05 18:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1993-06-05 18:45 Paul Haahr [this message]
  -- strict thread matches above, loose matches on Subject: below --
1993-06-07 17:10 Alan Watson
1993-06-07 15:24 Paul Haahr
1993-06-07  5:23 Alan Watson
1993-06-07  0:32 Paul Haahr
1993-06-05 18:59 Alan Watson
1993-06-05 18:38 Alan Watson

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=9306051845.AA04299@astro.mv.us.adobe.com \
    --to=haahr@mv.us.adobe.com \
    --cc=alan@oldp.astro.wisc.edu \
    --cc=rc@hawkwind.utcs.toronto.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).