From: Eric Mangold <teratorn@world-net.net>
To: Thorsten Kampe <thorsten@thorstenkampe.de>, zsh-users@sunsite.dk
Subject: Re: incremental history search
Date: Sat, 21 Feb 2004 16:56:56 -0700 [thread overview]
Message-ID: <opr3qvg6jci4eeqj@mail.oaktech.net> (raw)
In-Reply-To: <ofe9uo80gdem.dlg@thorstenkampe.de>
On Sat, 21 Feb 2004 16:50:48 +0100, Thorsten Kampe
<thorsten@thorstenkampe.de> wrote:
> * Anthony Iano-Fletcher (2004-02-21 15:39 +0100)
>> history-beginning-search-backward and history-beginning-search-forward
>> were designed to repeatedly match whatever was to the left of the cursor
>> with one's history. The cursor shouldn't move or else a repeated match
>> would not be looking for the original prefix.
>
> I know that, thanks. I was referring to the *special case where I
> haven't typed anything and the command line is empty* and there is
> *nothing to search for*.
If I just want to move up or down sequentially I use C-p and C-n. I guess
you need emacs bindings on for this (bindkey -me). These commands do
position the cursor at the end of the line.
> In this case "up-line-or-search" does simply
> a "up-line" and moves the cursor to the end of any recalled command
> line from history. "history-beginning-search-backward" does a
> "up-line", too, in this case, but leaves the cursor where it was (at
> the beginning of each recalled command line from history).
>
> Both approaches are useful in certain cases but in my opinion the
> dynamic movement to the end of the line is more useful because I
> manipulate the end of commands more often than the beginning.
>
> Thorsten
>
prev parent reply other threads:[~2004-02-21 22:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-20 23:04 Thorsten Kampe
2004-02-20 23:20 ` Björn Lindström
2004-02-21 0:54 ` Thorsten Kampe
2004-02-21 1:19 ` Philippe Troin
2004-02-21 2:43 ` Thorsten Kampe
2004-02-21 1:17 ` Eric Mangold
2004-02-21 1:35 ` Thorsten Kampe
2004-02-21 3:07 ` Eric Mangold
2004-02-21 13:52 ` Thorsten Kampe
2004-02-21 14:39 ` Anthony Iano-Fletcher
2004-02-21 15:50 ` Thorsten Kampe
2004-02-21 19:00 ` Bart Schaefer
2004-03-11 23:50 ` Thorsten Kampe
2004-02-21 23:56 ` Eric Mangold [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=opr3qvg6jci4eeqj@mail.oaktech.net \
--to=teratorn@world-net.net \
--cc=thorsten@thorstenkampe.de \
--cc=zsh-users@sunsite.dk \
/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).