From: Dave Mason <dmason@watmsg.waterloo.edu>
To: rc@archone.tamu.edu
Subject: RE: 'access' builtin for rc?
Date: Thu, 1 Aug 1991 16:35:11 -0500 [thread overview]
Message-ID: <9108012135.AA15337@watmsg.waterloo.edu> (raw)
In-Reply-To: Boyd Roberts's message of Thu, 1 Aug 1991 03:40:33 -0500 <9108011040.2131.rc.baden@prl.dec.com>
Boyd states it a little strongly, but I agree. Access looks nicer than
test, but it should be an executable, not a builtin. Perhaps it should ship
with rc (although is the extra functionality and clean-ness really worth the
incompatibility with test?), but in a bin library, please.
There are those of us who think that whatis should not be builtin. And the
only excuse for echo is that it's tiny and used a *lot*.
../Dave
prev parent reply other threads:[~1991-08-01 21:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1991-08-01 7:12 DaviD W. Sanderson
1991-08-01 8:40 ` Boyd Roberts
1991-08-01 14:13 ` Hamish Macdonald
1991-08-01 21:35 ` Dave Mason [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=9108012135.AA15337@watmsg.waterloo.edu \
--to=dmason@watmsg.waterloo.edu \
--cc=rc@archone.tamu.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).