From: Zoltan Hidvegi <hzoli@frontiernet.net>
To: pws@ifh.de (Peter Stephenson)
Cc: zsh-workers@math.gatech.edu
Subject: Re: compctl -X
Date: Tue, 5 Aug 1997 02:47:33 -0400 (EDT) [thread overview]
Message-ID: <199708050647.CAA01427@hzoli.home> (raw)
In-Reply-To: <199708041635.SAA00371@sgi.ifh.de> from Peter Stephenson at "Aug 4, 97 06:35:34 pm"
> I sent this some time ago, it seems to have disappeared...
>
> `compctl -X explanation' should print the explanation if there *are*
> matching completions, not if there aren't. If the type of matching
> wasn't used, you don't care; if it was, you want to know why.
It depends how do you use compctl -X. I used in in exatly the opposite
way: for example for dd, I complete filenames after if= but when I hit
TAB after bs= zsh will print <number> (see Misc/compctl-examples), and
that's always worked at least since zsh-2.5. Older versions had an
nmatches != 1 test here: if there is a unique completion, do it and do
not disturb the user. If there are no or more than one completions,
explain. It was an oversight from me (that I made last August, almost a
year ago) to change it. The patch below restores the original behaviour.
Zoltan
*** Src/Zle/zle_tricky.c 1997/06/16 05:20:01 3.1.3.1
--- Src/Zle/zle_tricky.c 1997/08/05 06:35:44
***************
*** 2127,2136 ****
}
/* Print the explanation string if needed. */
! if (!showinglist && expl && !nmatches) {
int up;
! feep();
trashzle();
clearflag = (isset(USEZLE) && !termflags &&
--- 2127,2137 ----
}
/* Print the explanation string if needed. */
! if (!showinglist && expl && nmatches != 1) {
int up;
! if (!nmatches)
! feep();
trashzle();
clearflag = (isset(USEZLE) && !termflags &&
next prev parent reply other threads:[~1997-08-05 7:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-08-04 16:35 Peter Stephenson
1997-08-05 6:47 ` Zoltan Hidvegi [this message]
1997-08-05 7:52 ` Peter Stephenson
-- strict thread matches above, loose matches on Subject: below --
1997-02-19 15:57 Peter Stephenson
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=199708050647.CAA01427@hzoli.home \
--to=hzoli@frontiernet.net \
--cc=pws@ifh.de \
--cc=zsh-workers@math.gatech.edu \
/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).