On 2021-08-18 10:23 a.m., Bart Schaefer wrote:
Sure, I expect that the functioning of options is now pretty much written in stone. One might contemplate some sort of radio button situation but it would just push the binary buttons lower down anyway.(1) The internals use 0/1 bitflags, and using multi-values would be both a lot of code changes and use more memory.
Yeah, one might temporarily disable various other things with 'noglob' which would restore things cleanly once it's cancelled. That makes sense. Still one might wish for some way of seeing what's actually active at any given time. 'setopt' shows us 'on' or 'off', but not 'disabled'. Dunno, the adept will have no need of such a thing but it could be educational. Many of my functions rely on Sebastian's 'znt' code and he resets options left right and center and I take most of it on faith, but being able to query the actual, functioning state of the options would be informative.(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