[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: GLOBIGNORE variable does not function when imported from environment
|
From: |
Chet Ramey |
|
Subject: |
Re: GLOBIGNORE variable does not function when imported from environment, until it's modified |
|
Date: |
Tue, 11 Apr 2017 09:21:23 -0400 |
|
User-agent: |
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 |
On 4/9/17 10:38 PM, Craig Strickland wrote:
> Bash Version: 4.3
> Patch Level: 30
> Release Status: release
>
> Description:
> The GLOBIGNORE variable, when not explicitly set, but only imported
> from the environment, does not function correctly.
> Once any change is made to the GLOBIGNORE variable, even setting it to
> its current value, then it works.
> This was reproduced with bash 4.3.30(1) on Debian 8.7 "jessie" as well
> as bash 4.3.39(1) on NetBSD 7.0.1.
Yes, GLOBIGNORE doesn't have any effect when it appears in the environment.
It makes shell scripts fail in erratic and unpredictable ways. If you
want to use GLOBIGNORE, you have to do something affirmative.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU chet@case.edu http://cnswww.cns.cwru.edu/~chet/