From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: Oliver Kiddle <okiddle@yahoo.co.uk>
Cc: zsh-workers <zsh-workers@zsh.org>
Subject: Re: Regression: broken completion on modification time
Date: Tue, 21 Jun 2016 01:41:32 +0000 [thread overview]
Message-ID: <20160621014132.GC17100@tarsus.local2> (raw)
In-Reply-To: <17354.1466180383@thecus.kiddle.eu>
Oliver Kiddle wrote on Fri, Jun 17, 2016 at 18:19:43 +0200:
> (As an aside, I notice _git has a max-verbose style. Not sure if we can
> change that for consistency with _path_commands.)
Change it how? I don't see how max-verbose and extra-verbose can be
combined, since the former is an int and the latter a bool.
> Daniel Shahaf wrote:
> > However, with this patch and extra-verbose, the «'' - exactly»
> > alternative doesn't show. (It's not just "hidden"; each of "- --
> > before" and "+ -- after" take half of $COLUMNS.)
>
> How would you want to present the exactly match given that it inserts
> nothing? In the past with the match -- description form, we didn't
> include it. With the description only form it is less out-of-place.
>
As you said later, it'd have to show as «'' -- exactly» or « --
exactly». (Or we could teach the C code to take '*(om=5)' for "exactly
five")
I mentioned the lack of "exactly" as a difference, but now that I think
about it, I suppose I think the "exactly" _should_ be displayed: firstly,
because displaying more options is better; secondly, because it is
displayed in non-verbose mode, and it'd be odd for setting the "verbose"
style to cause fewer options to be offered.
Another display option would be to use a dummy "string without a match"
as Bart said (compadd -E1) for something like
→ sense
(for the "exactly" sense, skip/omit this field)
+ -- before
- -- since
> > I tried to reproduce this in 'zsh -f', but «echo *(m<TAB>» simply cycled
> > between various integers after the 'm'; it didn't give the calendar
> > completion at all. It still did that with extra-verbose and
> > group-name='' set, I haven't debugged further yet.
>
> You need to enable menu selection:
> zstyle ':completion*:default' menu 'select=0'
> Pressing Ctrl-D (list-choices) a couple of times will also work.
Got it, thanks.
Daniel
next prev parent reply other threads:[~2016-06-21 1:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-12 20:32 Dima Kogan
2016-06-13 0:47 ` Bart Schaefer
2016-06-13 1:37 ` Dima Kogan
2016-06-13 22:00 ` Oliver Kiddle
2016-06-14 16:14 ` Bart Schaefer
2016-06-15 16:32 ` Oliver Kiddle
2016-06-15 23:24 ` Daniel Shahaf
2016-06-17 16:19 ` Oliver Kiddle
2016-06-17 18:11 ` Bart Schaefer
2016-06-17 19:10 ` Nikolay Aleksandrovich Pavlov (ZyX)
2016-06-17 22:02 ` Oliver Kiddle
2016-06-17 22:20 ` Nikolay Aleksandrovich Pavlov (ZyX)
2016-06-17 22:33 ` Bart Schaefer
2016-06-17 22:49 ` Nikolay Aleksandrovich Pavlov (ZyX)
2016-06-17 23:00 ` Bart Schaefer
2016-06-17 23:50 ` Oliver Kiddle
2016-06-19 16:04 ` Bart Schaefer
2016-06-21 1:41 ` Daniel Shahaf [this message]
2016-06-21 14:31 ` Oliver Kiddle
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=20160621014132.GC17100@tarsus.local2 \
--to=d.s@daniel.shahaf.name \
--cc=okiddle@yahoo.co.uk \
--cc=zsh-workers@zsh.org \
/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).