From: culliton@srg.af.mil (Tom Culliton x2278)
To: rc@hawkwind.utcs.toronto.edu
Subject: builtin time and read and ...
Date: Fri, 21 May 1993 17:04:35 -0400 [thread overview]
Message-ID: <9305211704.aa19691@ceres.srg.af.mil> (raw)
The last few months has seen the following "wish-list" items discussed:
builtin time (Malte)
builtin read (Alan Watson)
flag command (David J. Fiander)
. searching the path (David J. Fiander)
new options to whatis (Chris Siebenmann and me)
\ quoting (Malte)
comment changes (Malte)
~ expansion (Brendan Kehoe, et al.)
list exclusion syntax (Chris Siebenmann and Paul Haahr)
This list isn't even close to complete, and some reasonable ideas have
been offered, BUT we need to resist the temptation to add "just one more
feature" to rc, lest creeping featurism destroy us all. Note that I'm
not innocent, having agreed when Chris Siebenmann suggested adding
options to builtin whatis. (Maybe we all should join "Creeping Features
Anonymous".)
There are lots of things that rc doesn't have, job control, cd spell
checking, mailbox checking, command hashing, zillions of builtins, ...
We need to remember that this was a conscious design decision, and it
was exactly that elegant minimalism which attracted many of us to it.
Tom
reply other threads:[~1993-05-21 21:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=9305211704.aa19691@ceres.srg.af.mil \
--to=culliton@srg.af.mil \
--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).