Re: Globbing symlinks-to-${glob_qualifier}

[Bart Schaefer <schaefer@brasslantern.com>]

On Wed, Aug 18, 2021 at 9:48 AM Ray Andrews <rayandrews@eastlink.ca> wrote:
>
> This is a half baked musing as much as a question, but would it not be
> inevitable that some of these glob options

Note that the ones mentioning "global" are not glob options, and
"globcomplete" is a completion option rather than a globbing one.

> ... must contradict each other?  Options are always on/off, but wouldn't
> the logic of some of these settings be more of a 'radio button' sort of
> thing

Yes, there are a few cases where turning on option X causes option Y
to be ignored.  I think those cases are all properly documented, but
extra eyeballs on that sort of thing are never amiss.

There are two reasons we don't want to resort to having "radio button"
option behavior:
(1) The internals use 0/1 bitflags, and using multi-values would be
both a lot of code changes and use more memory.
(2) If you need to locally change X, it's not necessary to
save/restore any other state of Y that might interact with it.  A
prime example of this is "noglob" which obviously disavows a whole
fleet of other options, many of which are not otherwise mutually
exclusive.