From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-users@sunsite.dk
Subject: Re: Tip of the day: previous command output
Date: Sun, 22 Aug 2004 16:03:23 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.61.0408221538560.5997@toltec.zanshin.com> (raw)
In-Reply-To: <20040822212126.GN7841@ay.vinc17.org>
On Sun, 22 Aug 2004, Vincent Lefevre wrote:
> On 2004-08-20 21:25:47 -0700, Bart Schaefer wrote:
> >
> > Or you can get menu completion with
> >
> > zstyle ':completion:*' insert-kept menu
>
> I was talking about another kind of menu (which could be useful for
> standard completion too). For instance, there could be a cursor for
> the (standard zsh) menu, or perhaps a number, to be able to choose
> one or several word candidates.
>
> $ echo [TAB]
> [ab] ef ij
> cd gh kl
How is does this differ from menu selection?
Starting from my previous post, you need only add:
zmodload -i zsh/complist
zstyle ':completion:insert-kept-result:*' menu yes select
Then load something into $kept e.g. with "keep", and then type whatever
keystrokes you have insert-kept-result bound to.
If that doesn't correspond to the behavior you're describing above, then
there's something I'm still not understanding.
> or
>
> $ echo [TAB]
> 1 ab 3 ef 5 ij
> 2 cd 4 gh 6 kl
>
> then typing some key followed by the number would insert the word.
Numbering the possible matches is difficult, if not impossible, without
changing the guts of the completion C code, because the labels that may be
shown along with each match are assigned to the _possible_ matches, not to
the _actual_ matches. E.g. when completing files, compadd may be given
the name of every file in the directory, and then the completion internals
winnows them down to the names that actually fit the prefix or suffix
that's already on the line. So the numbers to show cannot be known until
immediately before the list is displayed, and hence can't be passed to
compadd by user-definable functions.
However, someone more ambitious than I might alter the complist module to
provide this display and some corresponding menuselect keymap bindings.
A question would be, what do you expect to happen when the list is too
long to fit on one screen?
next prev parent reply other threads:[~2004-08-22 23:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-19 8:58 Jesper Holmberg
2004-08-19 15:20 ` Bart Schaefer
2004-08-19 16:42 ` Andy Spiegl
2004-08-19 17:16 ` Bart Schaefer
2004-08-20 9:30 ` Andy Spiegl
2004-08-20 11:13 ` Vincent Lefevre
2004-08-20 12:12 ` Andy Spiegl
2004-08-20 14:50 ` Vincent Lefevre
2004-08-21 4:25 ` Bart Schaefer
2004-08-21 5:58 ` Bart Schaefer
2004-08-21 17:06 ` Bart Schaefer
2004-08-22 20:58 ` Vincent Lefevre
2004-08-23 1:10 ` Bart Schaefer
2004-08-23 13:51 ` Vincent Lefevre
2004-08-22 21:21 ` Vincent Lefevre
2004-08-22 23:03 ` Bart Schaefer [this message]
2004-08-23 13:00 ` Vincent Lefevre
2004-08-23 15:21 ` Bart Schaefer
2004-08-23 19:14 ` Vincent Lefevre
2004-08-26 23:16 ` Andy Spiegl
2004-08-27 0:43 ` Bart Schaefer
2004-08-27 10:21 ` Andy Spiegl
2004-08-31 15:03 ` zzapper
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=Pine.LNX.4.61.0408221538560.5997@toltec.zanshin.com \
--to=schaefer@brasslantern.com \
--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).