From: Boyd Roberts <boyd@prl.dec.com>
To: rc@archone.tamu.edu
Subject: Re: discussion about builtins
Date: Fri, 2 Aug 1991 05:54:42 -0500 [thread overview]
Message-ID: <9108021254.8883.rc.badom@prl.dec.com> (raw)
In-Reply-To: <9108021045.AA11404@dahlie.techfak.uni-bielefeld.de>
On one hand I appreciate the nice features of readline. On the other
readline multiplies the ressource usage of rc. My consequence was to
build two versions of rc, one with readline for interactive use, and one
without for use in shell scripts.
Isn't that a bug in readline? Shouldn't it realise what it's reading
and do the right thing? You don't need two rc's. That's absurd.
I still reckon that readline support should be removed, although it's lower
down on my `list of things to prevent'.
prev parent reply other threads:[~1991-08-02 10:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1991-08-02 10:45 malte
1991-08-02 10:54 ` Boyd Roberts [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=9108021254.8883.rc.badom@prl.dec.com \
--to=boyd@prl.dec.com \
--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).