On Feb 17 2019, Dennis Williamson wrote:
> Oh, interesting! In Bash 4 and 5, I just did declare -p with no args and it
> showed BASH_ALIASES empty. But with declare -p BASH_ALIASES it shows the
> contents (as does the alias command).
>
> Other arrays that show this difference for me:
>
> BASH_CMD
On Sun, Feb 17, 2019 at 8:23 PM Chet Ramey wrote:
> Thanks for the report. I'll fix it in the next devel branch push.
One more corner case, only shows up when bash is started by `login`:
$ set +m; exec /
-bash: /: Is a directory
-bash: exec: /: cannot execute: Is a directory
$ echo "$(ps -o pid,
On 2/18/19 12:55 PM, Grisha Levit wrote:
> On Sun, Feb 17, 2019 at 8:23 PM Chet Ramey wrote:
>> Thanks for the report. I'll fix it in the next devel branch push.
>
> One more corner case, only shows up when bash is started by `login`:
>
> $ set +m; exec /
> -bash: /: Is a directory
> -bash: exec
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
After. Prior to today's push bash just hangs after `exec /`.
Also I tested only on OSX, setting my login shell to the newly built bash
and setting iTerm/Terminal.app to use the login shell.
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