From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: Getting completion to tell the user what to do
Date: Tue, 20 Jul 1999 11:36:24 +0200 (MET DST) [thread overview]
Message-ID: <199907200936.LAA01843@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Bart Schaefer"'s message of Tue, 20 Jul 1999 09:23:54 +0000
Bart Schaefer wrote (to me):
> One last tidbit here:
>
> On Jul 20, 8:53am, Bart Schaefer wrote:
> } Subject: Re: Getting completion to tell the user what to do
> }
> } } Time for dirty tricks:
> } }
> } } compadd -UX 'Please...' -n ''
> } } compstate[insert]=''
> } } compstate[list]=list
> } } compstate[force_list]=yes
>
> I still don't understand why compstate[force_list]=yes doesn't do what it
> is documented to do, that is, force a listing even if there is only one
> match.
Oops, forgot that, sorry.
Yes, you are right, this is wrong.
Bye
Sven
diff -u os/Zle/zle_tricky.c Src/Zle/zle_tricky.c
--- os/Zle/zle_tricky.c Tue Jul 20 11:16:29 1999
+++ Src/Zle/zle_tricky.c Tue Jul 20 11:31:36 1999
@@ -4480,7 +4480,10 @@
minfo.cur = NULL;
minfo.asked = 0;
do_single(m->matches[0]);
- invalidatelist();
+ if (compforcelist && *compforcelist && uselist)
+ showinglist = -2;
+ else
+ invalidatelist();
}
} else {
invalidatelist();
diff -u od/Zsh/compwid.yo Doc/Zsh/compwid.yo
--- od/Zsh/compwid.yo Tue Jul 20 11:16:36 1999
+++ Doc/Zsh/compwid.yo Tue Jul 20 11:31:59 1999
@@ -212,7 +212,7 @@
a completion widget and may be changed there.
)
item(tt(force_list))(
-If the value for the tt(list) key is tt(ambiguous), the list will
+If the value for the tt(list) key is tt(autolist) or tt(ambiguous), the list will
normally be shown only if there are at least two matches in the
list. Setting tt(force_list) to an non-empty string forces the list to be
shown even if there is only one match.
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
reply other threads:[~1999-07-20 9:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=199907200936.LAA01843@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).