zsh-users
 help / color / mirror / code / Atom feed
From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: completion, sorting of options
Date: Fri, 10 Nov 2023 07:09:12 -0800	[thread overview]
Message-ID: <7da5aa87-d17f-4f59-91f6-78125917ac97@eastlink.ca> (raw)
In-Reply-To: <djdskidv7sdf37sikf8999uv5nee9221bp@tlc.com>

[-- Attachment #1: Type: text/plain, Size: 745 bytes --]


On 2023-11-10 06:04, Thomas Lauer wrote:
> 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.

Anyway, horse dead, flogging ends here. T

One more lash to the dead horse: It's another example of something being 
'too helpful'. But it's all water under the bridge now. As Bart says, 
too dangerous to tinker in the deepest entrails of the code. Still I do 
dream of zsh 6.0 where old traditions might be questioned, dead code cut 
out, compatibility with extinct shells no longer worried about, and so on.

[-- Attachment #2: Type: text/html, Size: 1415 bytes --]

  reply	other threads:[~2023-11-10 15:10 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
2023-11-10 15:09           ` Ray Andrews [this message]
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=7da5aa87-d17f-4f59-91f6-78125917ac97@eastlink.ca \
    --to=rayandrews@eastlink.ca \
    --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).