On Tue, 7 Jan 2025, 21:24 Tobi Laskowski, wrote:
> the issue starts with misusing SHELLOPTS.
Some folk have taken issue with my suggestion that SHELLOPTS is broken by
design. Perhaps that was hyperbole, but it seems to me that if all possible
uses for a feature actually constitute misuses, then
> This precdence question is really the only one. Is this issue serious
> enough to change previous behavior in an incompatible way?
To me it seems most intuitive for flags to be applied after the environment
variable, but I do not mind too much about this.
> No. That is not consistent with the
> This is already documented in a couple of different places:
Thanks for providing the relevant sections. This makes sense having read things
more thoroughly, however, most people do not read documentation from top to
bottom. Someone looking for a way to enable a shell option globally will likel
On Wednesday, January 8, 2025, Martin D Kealey
wrote:
>
> SHELLOPTS (such as debugging or delinting), but if it has no safe
> production use then perhaps that should be highlighted in the
> documentation.
>
Nah. A reminder that options enabled by the set command are inherited by
child shells when
