From: wez@twinklestar.demon.co.uk (Wez Furlong)
To: "Thomas Köhler" <jean-luc@picard.franken.de>
Cc: zsh-workers@math.gatech.edu
Subject: Re: Zle bug
Date: Mon, 2 Feb 1998 02:58:15 +0000 [thread overview]
Message-ID: <199802020258.CAA23535@twinklestar.demon.co.uk> (raw)
In-Reply-To: =?iso-8859-1?Q?Thomas_K=F6hler?= <jean-luc@picard.franken.de> "Re: Zle bug" (Feb 1, 3:41pm)
On Feb 1, 3:41pm, =?iso-8859-1?Q?Thomas_K=F6hler?= wrote:
> On Feb 1, Wez Furlong wrote
> > I am reporting a bug that is present in zsh 3.1.2 and also 3.1.2-zefram3.
> > Here's a demonstration:
> >
> > % > bindkey '\e[A' up-line-or-search
> > % > w
> > At this point I press cursor up
> > % > who
> > This is correct.
> I'd say "no, it's a bug" ;-)
> Looking at the manpages, I found this:
>
> up-line-or-search
> Move up a line in the buffer, or if already at the
> top line, search backward in the history for a line
> beginning with the first word in the buffer.
> Perhaps this can't be done in zsh-3.1.2 as it is now, we may need
> something like "up-line-or-history-beginning-search-backward". ;-)
[much snipping applied]
Hmm. I suppose you are right. I shall be changing to
history-beginning-search-backward (I don't often use multi-line editing).
The "up-line-or-history-beginning-search-backward" would be nice idea though.
__
Wez Furlong Undergrad - Electronic Systems Engineering
http://www.twinklestar.demon.co.uk
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
next reply other threads:[~1998-02-06 23:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-02-02 2:58 Wez Furlong [this message]
[not found] <aheading@jpmorgan.com>
1998-02-09 13:23 ` Wez Furlong
-- strict thread matches above, loose matches on Subject: below --
1998-02-01 3:16 Wez Furlong
1998-02-01 14:41 ` Thomas Köhler
1998-02-09 12:57 ` Anthony JR Heading
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=199802020258.CAA23535@twinklestar.demon.co.uk \
--to=wez@twinklestar.demon.co.uk \
--cc=jean-luc@picard.franken.de \
--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).