From: Thomas Lauer <thomas.lauer@virgin.net>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: completion, sorting of options
Date: Fri, 10 Nov 2023 14:04:13 +0000 [thread overview]
Message-ID: <djdskidv7sdf37sikf8999uv5nee9221bp@tlc.com> (raw)
In-Reply-To: <CAH+w=7bY9d+GRW5E=zvsHSKQODykMTySi+hkYH72irF8bmycYw@mail.gmail.com>
From: Bart Schaefer <schaefer@brasslantern.com>
Date: Thu, 9 Nov 2023 10:07:16 -0800
> On Thu, Nov 9, 2023 at 5:32?AM Thomas Lauer <thomas.lauer@virgin.net> wrote:
>
> > It's just a bit frustrating that what I'd call an
> > implementation detail within _arguments makes this call perform in a way
> > a (probably naive) user doesn't expect and can't easily grok or rectify.
>
> Combination of an unanticipated use case and the order in which
> features like unsorted groups were added to "compadd" relative to the
> implementation of _arguments.
Weeeellllll, unanticipated use case... that's debatable IMO. Obviously
somebody thought that a no-sort option would be a good idea, in fact
such a good idea that there are two ways to do it. But what they then
proceeded to do was to have the nosort option sort just a tiny little
bit anyway, for good measure. In my book that's not an unanticipated use
case but questionable design.
I am an old-fashioned git and think that an option should do what it
says on the tin. I'd readily accept that "sort false" does the tiny
little bit anyway, but then nosort should definitely switch sorting off
completely (or vice versa).
Anyway, horse dead, flogging ends here. T
next prev parent reply other threads:[~2023-11-10 14:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-04 15:42 Thomas Lauer
2023-11-04 15:49 ` Mikael Magnusson
2023-11-05 15:02 ` Thomas Lauer
2023-11-05 15:58 ` Bart Schaefer
2023-11-05 16:58 ` Thomas Lauer
2023-11-08 13:24 ` Thomas Lauer
2023-11-08 20:09 ` Bart Schaefer
2023-11-08 20:44 ` Ray Andrews
2023-11-08 21:34 ` Bart Schaefer
2023-11-08 22:41 ` Ray Andrews
2023-11-09 13:32 ` Thomas Lauer
2023-11-09 18:07 ` Bart Schaefer
2023-11-10 14:04 ` Thomas Lauer [this message]
2023-11-10 15:09 ` Ray Andrews
2023-11-10 17:15 ` 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=djdskidv7sdf37sikf8999uv5nee9221bp@tlc.com \
--to=thomas.lauer@virgin.net \
--cc=schaefer@brasslantern.com \
--cc=zsh-users@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).