On 2/18/19 1:44 PM, L A Walsh wrote:
>
>
> On 2/17/2019 6:54 PM, Chet Ramey wrote:
>> Not quite. Dynamic variables are only defined to return the correct value
>> when they are referenced. The rest of the time, the values are
>> indeterminate (and possibly stale). The idea is that you can get an
On 2/17/2019 6:54 PM, Chet Ramey wrote:
> Not quite. Dynamic variables are only defined to return the correct value
> when they are referenced. The rest of the time, the values are
> indeterminate (and possibly stale). The idea is that you can get an element
> given the right index, or all the e
On 2/16/19 7:57 AM, Robert Elz wrote:
> Date:Fri, 15 Feb 2019 22:21:25 -0800
> From:L A Walsh
> Message-ID: <5c67abe5.1030...@tlinx.org>
>
> | Thought about thatrestarted a fresh shell. Same same.
> | At least I know it's supposed to...
>
> It isn't just
On 2/15/19 11:45 PM, L A Walsh wrote:
>
> I printed the various declares using:
>
> declare -p |& more
>
> One of the early entries is:
>
> declare -A BASH_ALIASES=()
>
> Yet if I type 'alias |& wc, I see 56 lines starting with alias.
>
> I _thought_ BASH_ALIASES was suppose to hold the alias
Date:Fri, 15 Feb 2019 22:21:25 -0800
From:L A Walsh
Message-ID: <5c67abe5.1030...@tlinx.org>
| Thought about thatrestarted a fresh shell. Same same.
| At least I know it's supposed to...
It isn't just BASH_ALIASES - you'll see the same from lots of
other
On 2/15/2019 9:32 PM, Dennis Williamson wrote:
>
>
>
>
> It's likely that somewhere your BASH_ALIASES has been unset. See the
> manual section quoted here:
>
> |BASH_ALIASES|
>
> An associative array variable whose members correspond to the
> internal list of aliases as maintained
On Fri, Feb 15, 2019, 10:46 PM L A Walsh
> I printed the various declares using:
>
> declare -p |& more
>
> One of the early entries is:
>
> declare -A BASH_ALIASES=()
>
> Yet if I type 'alias |& wc, I see 56 lines starting with alias.
>
> I _thought_ BASH_ALIASES was suppose to hold the aliases
>
