Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: NO_CASE_GLOB and unreadable directories (Episode VI: A New Hope)
- X-seq: zsh-workers 47872
- From: Peter Stephenson <p.w.stephenson@xxxxxxxxxxxx>
- To: zsh-workers@xxxxxxx
- Subject: Re: NO_CASE_GLOB and unreadable directories (Episode VI: A New Hope)
- Date: Mon, 25 Jan 2021 14:05:49 +0000 (GMT)
- Archived-at: <https://zsh.org/workers/47872>
- Archived-at: <http://www.zsh.org/sympa/arcsearch_id/zsh-workers/2021-01/1009925809.3264416.1611583549597%40mail2.virginmedia.com>
- Importance: Medium
- In-reply-to: <CAH+w=7aLB+wHaZe=dedrmdVxvqQjMMk4vFz99rKCAadtNzgbqw@mail.gmail.com>
- List-id: <zsh-workers.zsh.org>
- References: <CAEtFKssJf-cN_EM+=5_10seY58jqALV-YH8+z5+Lm-04v493Nw@mail.gmail.com> <CAH+w=7bn8JYPx29LPGnT4ughEt-z+-rUokUz739foP=JCY9B7g@mail.gmail.com> <CAEtFKssJVz9mr3vA_vY77m2bsrXWBKHz1qgv83jzeY0jLXzPjQ@mail.gmail.com> <CAH+w=7aoaGhVCqZQ6K+z0HqJg3agOav6bh6M_9pg464aAC+htQ@mail.gmail.com> <CAH+w=7Y5UQDd7Xn6g9MR_oYtDFw8S-2WpX7xEehPZ9y47=ex8w@mail.gmail.com> <CAH+w=7aLB+wHaZe=dedrmdVxvqQjMMk4vFz99rKCAadtNzgbqw@mail.gmail.com>
> On 25 January 2021 at 00:52 Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx> wrote:
> I see these possibilities:
> 1) Do nothing; Devin's case is broken by design and termux needs to
> come up with a solution that doesn't involve NO_CASE_GLOB.
> 2) Adopt (a CYGWIN-clean variant of) my patch from workers/47832, and
> accept that some current usage of NO_CASE_GLOB will break.
> 3) Add a setopt (CASE_DIRS ?) for the current behavior, and merge that
> with workers/47832. I haven't yet worked out how to avoid having
> "setopt nocasedirs" imply the effects of "setopt nocaseglob" ...
> perhaps name it CASE_SEARCH (?) and simply leave the implication?
I don't think 2) is so unreasonable in that only patterns with some
form of case-insensitivity are involved. This is something of a minefield
at the best of times and getting something that looks natural on systems
that are intrinsically case-insensitive, whether or not case-preserving,
is difficult. But with a new option it seems to provide a definite path
forward in any case. The only serious objection to that other that I
can see is that it makes the code more complicated; the reply to that is
if the code is simple there's a good chance it doesn't quite do what you
need it to.
(For the same reasons I'm not actually commenting on the details, since
I'm well aware how easy it is to miss some crucial aspect.)
pws
Messages sorted by:
Reverse Date,
Date,
Thread,
Author