From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: PATCH: RE: side effect of "select=long"
Date: Mon, 22 May 2000 14:20:34 +0200 (MET DST) [thread overview]
Message-ID: <200005221220.OAA20330@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Andrej Borsenkow"'s message of Mon, 22 May 2000 15:44:03 +0400
Andrej Borsenkow wrote:
> Not at all. We have separately completion lists AND menu
> completion/selection. First list is displayed (of course, with
> corresponding settings) and then, on the second TAB, menu
> completion/selection is started. So, that means `start selection INSTEAD
> of list if matches do not fit on the screen and start selection ON THE
> SECOND TAB always (assuming, it was not started already)'.
That's what I wanted to make possible. There was a thinko in the code,
though, sorry. The incantation is, of course:
zstyle ':completion:*' menu 'select=0' 'select=long-list'
Ok?
Bye
Sven
Index: Completion/Core/_main_complete
===================================================================
RCS file: /cvsroot/zsh/zsh/Completion/Core/_main_complete,v
retrieving revision 1.24
diff -u -r1.24 _main_complete
--- Completion/Core/_main_complete 2000/05/22 12:14:37 1.24
+++ Completion/Core/_main_complete 2000/05/22 12:20:49
@@ -159,9 +159,9 @@
_menu_style=( "$_menu_style[@]" "$_def_menu_style[@]" )
- if [[ -z "$compstate[insert]" ]]; then
- [[ -n "$_menu_style[(r)select=long-list]" && tmp -gt LINES ]] &&
- compstate[insert]=menu
+ if [[ "$compstate[list]" = *list &&
+ -n "$_menu_style[(r)select=long-list]" && tmp -gt LINES ]]; then
+ compstate[insert]=menu
elif [[ "$compstate[insert]" = "$_saved_insert" ]]; then
if [[ -n "$_menu_style[(r)select=long]" && tmp -gt LINES ]]; then
compstate[insert]=menu
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~2000-05-22 12:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-22 12:20 Sven Wischnowsky [this message]
2000-05-22 12:48 ` Andrej Borsenkow
2000-05-22 13:44 ` Still problems " Andrej Borsenkow
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=200005221220.OAA20330@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--cc=zsh-workers@sunsite.auc.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).