From: dana <dana@dana.is>
To: Zsh workers <zsh-workers@zsh.org>
Subject: Re: completion match ordering
Date: Mon, 26 Nov 2018 17:07:40 -0600 [thread overview]
Message-ID: <CFE56814-4349-44CF-BE0B-9BF9E81827EB@dana.is> (raw)
In-Reply-To: <76839-1543195550.251964@c6AU.RX4q.p78d>
On 25 Nov 2018, at 19:25, Oliver Kiddle <okiddle@yahoo.co.uk> wrote:
>Any thoughts on the interface? Is something more terse like -on
>preferable?
Experimenting with it in (what would be) 'real-world' applications, i do find it
kind of wordy, and if/when additional ordering options (like reverse) are added
it'll be even more so. Maybe a compromise would be possible, where the ordering
options can be abbreviated like -onum,rev? I could be over-complicating it,
though.
On 25 Nov 2018, at 19:25, Oliver Kiddle <okiddle@yahoo.co.uk> wrote:
>Besides match, nosort and numeric, should any other orderings be
>supported? Reverse or case-sensitive perhaps?
I like the idea of reverse and case modifiers as i mentioned in our other
conversation. But i suppose in a lot of cases it'll be simple enough to just do
`compadd -o nosort - ${(Oi)foo}` or whatever, so... it'd be cool, but not
necessarily critical.
Other than that, i didn't test *super* extensively, but it seems to work well
for the sort of thing that inspired my original question (keeping numbers in the
right order, as in _lz4).
dana
next prev parent reply other threads:[~2018-11-26 23:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-04 0:13 [PATCH] Completion: Sort lz4 compression levels properly (+ a question) dana
2018-11-07 10:35 ` Oliver Kiddle
2018-11-07 17:52 ` dana
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 [this message]
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=CFE56814-4349-44CF-BE0B-9BF9E81827EB@dana.is \
--to=dana@dana.is \
--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).