Re: [BUG] 'unset' fails silently under specific conditions

From	Martijn Dekker <martijn@inlv.org>
Newsgroups	gnu.bash.bug
Subject	Re: [BUG] 'unset' fails silently under specific conditions
Date	2018-05-02 15:48 +0100
Message-ID	<mailman.13280.1525272515.27995.bug-bash@gnu.org> (permalink)
References	(4 earlier) <48f7a2c2-70ce-0994-33e0-6b2282a3b5f6@inlv.org> <aa36f1ca-ca58-ebee-4f95-2e76e5221721@case.edu> <d87ee315-f35d-67e5-32a7-44d40110b5fd@inlv.org> <20180502143252.gie2em6535qbrlfu@eeg.ccf.org> <20180502143829.2jgim7ho24nc5t6q@eeg.ccf.org>

Show all headers | View raw

Op 02-05-18 om 15:38 schreef Greg Wooledge:
> *NOW* there's evidence of a local variable, because unset removes it
> and exposes the global.

Right. That's what triggered my initial report, in which I confused that 
phenomenon for a failure of the 'unset' command to unset the variable.

>   But it's not "permanently exported" as far as  I can see.

Sorry for the inexact use of language -- I simply meant that the global 
scope of the variable acquired the export flag, as opposed to the 
function-local scope.

- M.

Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread

Thread

Re: [BUG] 'unset' fails silently under specific conditions Martijn Dekker <martijn@inlv.org> - 2018-05-02 15:48 +0100

csiph-web