From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: Question about _history-complete-older
Date: Thu, 26 Jan 2012 23:51:14 -0800 [thread overview]
Message-ID: <120126235114.ZM2826@torch.brasslantern.com> (raw)
In-Reply-To: <jfs8fe$37t$1@dough.gmane.org>
On Jan 26, 8:10pm, Bernhard Tittelbach wrote:
}
} In my zsh version 4.3.11, _history-complete-newer completes a word from
} the history, beginning with the oldest words in the history,
} while _history-complete-older completes a word from history starting
} with the most recent entries.
That's because they wrap around if they don't find anything. So if
you do "newer" starting from the end, it will immediately find nothing
and then wrap to the beginning and start from there; similarly "older"
from the end (most recent) will work backward from there.
Thus "newer" and "older" are relative to the entry on which you start
searching, not relative to each other; they refer to the direction of
the search, not to the recency of the entries they find.
If you don't want it to wrap around, you set the "stop" style:
stop
If set to `true', the _history_complete_word bindable command will
stop once when reaching the beginning or end of the history.
Invoking _history_complete_word will then wrap around to the
opposite end of the history. If this style is set to `false' (the
default), _history_complete_word will loop immediately as in a
menu completion.
There ought to be an example for this, but there isn't, so:
zstyle :completion:*:history-words stop yes
Also the I see the description for the "list" style is incorrect;
it says:
The context always starts with `:completion:history-words'.
In fact the context always starts with :completion: and always ENDS
with :history-words, but there may be more context in between.
next prev parent reply other threads:[~2012-01-27 7:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 19:10 Bernhard Tittelbach
2012-01-27 7:51 ` Bart Schaefer [this message]
2012-01-27 15:17 ` Bernhard Tittelbach
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=120126235114.ZM2826@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@zsh.org \
/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).