On 7/30/22 8:05 AM, Kerin Millar wrote:
What consideration was given to creating “local --unset *VAR*” or “unset
--local *VAR*” or some other equivalent that doesn't overload any existing
command form?
Obviously, only Chet can meaningfully respond to this. I mentioned the
existence of the option because it appeared likely that Emanuele was unaware of
it, not to attempt to obviate any of his suggestions, nor endorse the status
quo.
Sometimes it's useful to read the discussion that prompted the change.
https://lists.gnu.org/archive/html/bug-bash/2018-02/msg00065.html
In this case, the primary requirement was to enable scripts that wanted a
wholesale behavior change, while not breaking backwards compatibility by
making that option the default. Enabling these semantics on a per-variable
basis wasn't part of the discussion (kre was, however, very vocal about
making localvar_unset the default).
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU c...@case.edu http://tiswww.cwru.edu/~chet/