From: Steve Kilbane <steve@whitecrow.demon.co.uk>
To: rc@hawkwind.utcs.toronto.edu
Subject: Re: rc futures
Date: Sun, 19 Dec 1999 06:06:54 -0500 [thread overview]
Message-ID: <199912191106.LAA30430@whitecrow.demon.co.uk> (raw)
In-Reply-To: Your message of "Thu, 16 Dec 1999 12:43:13 GMT." <19991216124313.10637.qmail@pantransit.reptiles.org>
When Tim mentioned "rc 2", I have to admit I was expecting something along
the lines of "same functionality, 'better' internals". The amount and
size of some of the changes being discussed is scary. ( different syntax,
different variable handling, different execution semantics, and different
input behaviour, and bigger, but otherwise business as usual ). And as
Paul/Byron said, if you want some of this, go use es.
The only one that makes sense to me is the error messages. I'd favour
"rc:" on the command line, and "script-name:" for scripts. If you were
going to always include "rc:", I'd want a space after it, so that it didn't
confuse wily with "rc:script:nn".
I'm not familiar with readline and its variants, having never explicitly
gone out looking for it. Does it provide anything other than history
recall and editing? If not, $history is enough to provide 99% of that
functionality via an external program.
steve
next prev parent reply other threads:[~1999-12-21 23:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-16 12:43 Smarasderagd
1999-12-19 11:06 ` Steve Kilbane [this message]
1999-12-22 0:00 ` Christopher Vance
-- strict thread matches above, loose matches on Subject: below --
2000-01-14 12:20 Bengt Kleberg
2000-01-14 12:16 Bengt Kleberg
2000-01-12 21:34 Chet Ramey
2000-01-01 2:55 ` Paul Haahr
2000-01-12 14:22 Bengt Kleberg
2000-01-03 15:46 Bengt Kleberg
1999-12-16 16:40 Chet Ramey
1999-12-15 16:32 Russ Cox
1999-12-14 9:44 Byron Rakitzis
1999-12-13 12:55 Elliott Hughes
1999-12-10 16:55 Tim Goodwin
1999-12-13 18:54 ` Paul Haahr
2000-01-04 16:43 ` Tim Goodwin
1999-12-31 23:26 ` Paul Haahr
1999-12-15 0:17 ` Chris Siebenmann
2000-01-07 3:45 ` Decklin Foster
2000-01-01 4:20 ` Paul Haahr
2000-01-15 8:58 ` Steve Kilbane
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=199912191106.LAA30430@whitecrow.demon.co.uk \
--to=steve@whitecrow.demon.co.uk \
--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).