Date:Tue, 27 Feb 2018 11:18:40 -0500
From:Chet Ramey
Message-ID: <21679c48-4064-5683-2d5f-91bfb7668...@case.edu>
| It doesn't. Run the following script:
OK, that looks good. But now I am very confused.
| You'll see that the first expansion of `$var' uses the lo
On 2/27/18 11:23 AM, Chet Ramey wrote:
> On 2/26/18 11:34 AM, Robert Elz wrote:
>
>> I believe that most shells that implement local (which is most shells)
>> implement unset of a local as meaning the local var becomes unset,
>> not that it vanishes and the global reappears.
>
> That was the obj
Chet, thanks for the suggestion.
i still wonder what's the objection to changing .gitignore?
using a separate directory to build, while i'm working on the sources,
feels less convenient.
On Sun, Feb 25, 2018 at 1:10 PM, Chet Ramey wrote:
> On 2/25/18 2:49 PM, don fong wrote:
> > Chet, i'm
On 2/26/18 11:34 AM, Robert Elz wrote:
> I believe that most shells that implement local (which is most shells)
> implement unset of a local as meaning the local var becomes unset,
> not that it vanishes and the global reappears.
That was the objection: that unset in a function unset the local i
On 2/26/18 9:57 AM, Clint Hepner wrote:
> As you say, the intent is to use a particular value of the variable. The fact
> that unsetting
> IFS causes it to use a default value other than an empty string seems more
> like a concession
> to historical usage than a feature that should be explicitly
On 2/26/18 4:31 AM, Robert Elz wrote:
> Date:Mon, 12 Feb 2018 09:26:37 -0500
> From:Chet Ramey
> Message-ID: <790ade74-690f-541c-9ab4-635991744...@case.edu>
>
> | This is bash's dynamic scoping. The visibility of a local variable is
> | restricted to a function an
