From: dana <dana@dana.is>
To: Oliver Kiddle <okiddle@yahoo.co.uk>
Cc: Zsh workers <zsh-workers@zsh.org>
Subject: Re: [PATCH] Completion: Sort lz4 compression levels properly (+ a question)
Date: Wed, 7 Nov 2018 11:52:39 -0600 [thread overview]
Message-ID: <3DB20542-4CD9-42DD-B324-0F5B62AAD10E@dana.is> (raw)
In-Reply-To: <88812-1541586959.338018@YaNA.ZOZt.NKaA>
On 7 Nov 2018, at 04:35, Oliver Kiddle <okiddle@yahoo.co.uk> wrote:
>The compadd interface perhaps isn't ideal. If -V was a standalone option
>like -1 and -2, intended to be used in combination with -J (to specify
>the group name), then it would be easier to modify the sort order.
Yeah, i don't know the history behind it, but i've found myself thinking exactly
that several times.
On 7 Nov 2018, at 04:35, Oliver Kiddle <okiddle@yahoo.co.uk> wrote:
>Can we improve it without breaking backward compatibility. -o with an
>argument could allow for more sorting options, e.g. -o numeric to do
>numeric sorting. Do we need to be concerned that someone somewhere may
>actually be using -o?
I can't find any instances of it in either the main zsh repo or the
zsh-completions one, nor in any of the 'vendor completions' i have installed on
my Mac or Ubuntu machines, so i bet you're right that it's not been used.
Are you suggesting removing the requirement to use it with -d, and giving it an
optarg to control the match-string sorting method?
dana
next prev parent reply other threads:[~2018-11-07 17:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-04 0:13 dana
2018-11-07 10:35 ` Oliver Kiddle
2018-11-07 17:52 ` dana [this message]
2018-11-26 1:25 ` completion match ordering Oliver Kiddle
2018-11-26 3:09 ` Daniel Shahaf
2018-11-26 5:18 ` dana
2018-11-26 9:37 ` Peter Stephenson
2018-11-26 23:07 ` dana
2019-05-06 21:16 ` PATCH: " Oliver Kiddle
2019-05-07 0:10 ` dana
2019-05-07 12:39 ` Oliver Kiddle
2019-08-22 8:39 ` Daniel Hahler
2019-08-23 19:05 ` Oliver Kiddle
2019-08-25 14:25 ` Daniel Hahler
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=3DB20542-4CD9-42DD-B324-0F5B62AAD10E@dana.is \
--to=dana@dana.is \
--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).