From: Anthony Heading <anthony.j.heading@jpmorgan.com>
To: Andrew Main <zefram@tao.co.uk>
Cc: Anthony Heading <aheading@jpmorgan.com>, zsh-workers@math.gatech.edu
Subject: Re: up-line-or-search still 'fixed'!
Date: Tue, 9 Jun 1998 14:13:04 +0100 [thread overview]
Message-ID: <19980609141304.41665@gmp-fores1.uk.jpmorgan.com> (raw)
In-Reply-To: <199804281408.PAA32237@taos.demon.co.uk>; from Andrew Main on Tue, Apr 28, 1998 at 03:08:04PM +0100
On Tue, Apr 28, 1998 at 03:08:04PM +0100, Andrew Main wrote:
> Yes. That's why I'm unwilling to go back to the old behaviour.
> The behaviour of up-line-or-search used to depend on whether the
> immediately preceding editing command was also up-line-or-search.
> The model I'm trying to move ZLE to has the effects of each editing
> command as independent as possible of other commands, so that eventually
> most of them can be separated into modules or even implemented purely
> as shell functions. Each of the ZLE_* flags violates this principle to
> some extent, so I'm trying to remove them as far as possible (which will
> not be completely).
[...]
> But for the moment it just doesn't fit into the ZLE architecture.
>
> How would people feel about making up-line-or-search do a
> history-beginning-search-backwards? This would be a lot closer to the
> old behaviour, differing only in the resulting cursor position.
OK. I've done my best to live with this for six weeks. But it just isn't
working for me. This was a really major feature for anyone who had it
turned on, and having read the code now, IMHO the hit far outweighed the
benefits of a fractionally less broken architecture: it was doing no real
harm until it was the last of the residual state variables.
So I really must protest. This is purism over usability!
Thus unfortunately, I'm going to have to switch back to 3.0.5 until
the brave new dawn.
--
Anthony J.R. Heading J.P. Morgan & Co. Inc, Singapore
Email: heading_anthony@jpmorgan.com Tel: +65 326 9027
next prev parent reply other threads:[~1998-06-09 13:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <aheading@jpmorgan.com>
1998-02-09 13:23 ` Zle bug Wez Furlong
1998-04-28 12:34 ` up-line-or-search still 'fixed'! Anthony Heading
1998-04-28 13:21 ` Andy Wick
1998-04-28 13:33 ` Anthony Heading
1998-04-28 14:08 ` Andrew Main
1998-06-09 13:13 ` Anthony Heading [this message]
1998-06-09 15:22 ` Bart Schaefer
1998-06-09 15:50 ` Bruce Stephens
1998-06-09 18:42 ` Bart Schaefer
1998-06-10 10:14 ` Bruce Stephens
1998-06-10 10:31 ` Zefram
1998-06-10 11:57 ` Bruce Stephens
1998-06-10 17:13 ` Bart Schaefer
1998-06-10 5:18 ` message numbers in mla Geoff Wing
1998-06-22 11:16 ` Geoff Wing
1998-06-22 16:17 ` Bart Schaefer
1998-06-22 17:38 ` Richard Coleman
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=19980609141304.41665@gmp-fores1.uk.jpmorgan.com \
--to=anthony.j.heading@jpmorgan.com \
--cc=aheading@jpmorgan.com \
--cc=zefram@tao.co.uk \
--cc=zsh-workers@math.gatech.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).