From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: Re: (forw) --help able programs and completion]
Date: Wed, 28 Jun 2000 09:08:04 +0200 (MET DST) [thread overview]
Message-ID: <200006280708.JAA30587@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Bart Schaefer"'s message of Tue, 27 Jun 2000 15:46:04 -0700
Bart Schaefer wrote:
> On Jun 27, 5:02pm, Sven Wischnowsky wrote:
> > Subject: PATCH: Re: (forw) --help able programs and completion]
> >
> > Bart Schaefer wrote:
> >
> > > What I was expecting, for some reason, was that menu selection would start
> > > immediately if there were more than N matches, not wait for the second TAB
> > > that triggers automenu.
> >
> > Ah. No, but that's easy to add.
>
> Er, thanks, but you didn't really need to add that; all I wanted was a
> yes-or-no answer ...
It was fun writing it (and I needed something to distract me from real
work).
> > I used the same form as for `select', i.e. one can say `yes=3' to turn
> > on menu completion when there are at least three matches.
>
> Hrm.
> zstyle ':completion:*' menu 1=3
>
> Does that look a bit strange to anyone else?
Yes, to me (I wondered if I should point that out yesterday). But with
the select[=val] in place this looked like a easy-to-understand
enhancement.
Another question is if it should mean `if there are less than <num>
matches, start menu completion', because menu completion (at least the
*real* menu completion, not selection) works best with few matches.
That's easy to change, though (I'd like to get opinions from menu
completion users).
> > Does anybody now want support for `no=3'?
>
> Which would mean ...?
If one has `setopt menucomplete', setting the menu style to one of the
`false' values can be used to turn menu completion off for some
contexts. Allowing `no=<num>' would either mean to turn it of if there
are more or less than <num> matches, whatever we decide `yes=<num>'
means.
> However, a plain-ol'-menu-completion variant of select=long-list might be
> interesting.
Hmhm, right.
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~2000-06-28 7:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-28 7:08 Sven Wischnowsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-06-29 9:27 Sven Wischnowsky
2000-06-29 7:02 Sven Wischnowsky
2000-06-29 9:04 ` Peter Stephenson
[not found] <200006271502.RAA30019@beta.informatik.hu-berlin.de>
2000-06-27 22:46 ` Bart Schaefer
2000-06-27 15:06 Sven Wischnowsky
2000-06-27 13:18 Sven Wischnowsky
2000-06-27 15:02 ` Bart Schaefer
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=200006280708.JAA30587@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).