From: Chris Siebenmann <cks>
Subject: changes to rc
Date: Fri, 17 Sep 1993 15:50:32 -0400 [thread overview]
Message-ID: <93Sep17.firstname.lastname@example.org> (raw)
I have a suggestion for people proposing changes to rc: the best way to
persuade people that it's a good idea is to implement it in your version
and then post the code so other people can try it out. We can argue for
ages about the merits of various features, but we're doing it in a vaccum.
For example, I'd imagine that a builtin read would be much more likely
to be accepted if someone produced a good implementation of it (say,
one that respected IFS and so on), and posted said implementation. I know
I'd stick it into my version.
next reply other threads:[~1993-09-17 19:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-09-17 19:50 Chris Siebenmann [this message]
1993-09-19 13:32 raymondc
1993-09-19 20:48 Byron Rakitzis
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 \
* 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).