From: Chris Siebenmann <cks@hawkwind.utcs.toronto.edu>
To: rc@archone.tamu.edu
Subject: Re: editline
Date: Sat, 8 Feb 1992 21:34:38 -0600 [thread overview]
Message-ID: <92Feb8.223441est.2732@hawkwind.utcs.toronto.edu> (raw)
In-Reply-To: dylan's message of Sat, 08 Feb 92 17:49:44 -0500. <9202082249.AA05482@ibmpcug.co.uk>
I once put 'merge command sequences' into a history recall (in fact,
wrote it in in the first place). After a month or so of use, I ripped
it out and was much happier. My experience was that it causes a
'dissonance'; what you remember typing is not what you will get with
command recall, and this fouls up one's reflexes. I would heavily
recommend against adding this feature.
- cks
next prev parent reply other threads:[~1992-02-09 3:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1992-02-08 22:49 editline Matthew Farwell
1992-02-09 3:34 ` Chris Siebenmann [this message]
-- strict thread matches above, loose matches on Subject: below --
1992-02-08 16:08 editline malte
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=92Feb8.223441est.2732@hawkwind.utcs.toronto.edu \
--to=cks@hawkwind.utcs.toronto.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).