From: Alan Watson <alan@oldp.astro.wisc.edu>
To: haahr@mv.us.adobe.com (Paul Haahr)
Cc: rc@hawkwind.utcs.toronto.edu
Subject: Re: redirection and built-ins
Date: Mon, 7 Jun 1993 01:23:47 -0400 [thread overview]
Message-ID: <9306070523.AA07327@oldp.astro.wisc.edu> (raw)
| ``echo ... | read foo'' is not the appropriate construct in rc or es.
Yeah, because it doesn't work; there is nothing intrinsicly
`inappropriate' about it. I hadn't realised there was a lexicon of
politically correct idioms in rc, but clearly I have been badly
misinformed...
| read hasn't made it to either of these shells yet. why are we talking
| about modifying fundamental parts of these shells to support inappropriate
| uses of (as-yet) unimplemented operations?
Sorry, I didn't actually mean to imply that read should be a built-in,
and I was actually thinking of a functionally-implemented read. When
I mentioned rc forking to provide redirection for built-ins, I was
also thinking about functions, but it was sloppy writing on my part.
next reply other threads:[~1993-06-07 5:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-06-07 5:23 Alan Watson [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 0:32 Paul Haahr
1993-06-05 18:59 Alan Watson
1993-06-05 18:45 Paul Haahr
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=9306070523.AA07327@oldp.astro.wisc.edu \
--to=alan@oldp.astro.wisc.edu \
--cc=haahr@mv.us.adobe.com \
--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).