On Wed, 30 Sep 2020 09:19:34 -0400 Chet Ramey wrote:
...
> I explained the reasoning in
>
> https://lists.gnu.org/archive/html/bug-bash/2016-11/msg00165.html
...
The reasoning is 100% sound, but would it make sense to add the old behavior to
a compat option? I'm not at all familiar with the dec
On 9/30/20 12:28 AM, Jason Miller wrote:
> Gentoo linux, GNU bash, version 5.0.18(1)-release (x86_64-pc-linux-gnu)
>
> On the above vesion of bash, the following script will not run the echo
> command
> and print an error. On bash 4.4 it appears to treat the ${!foo} the same as
> expanding an u
On Tue, 29 Sep 2020 21:28:59 -0700, Jason Miller wrote:
> Gentoo linux, GNU bash, version 5.0.18(1)-release (x86_64-pc-linux-gnu)
>
> On the above vesion of bash, the following script will not run the echo
> command and print an error. On bash 4.4 it appears to treat the ${!foo}
> the same as e
Gentoo linux, GNU bash, version 5.0.18(1)-release (x86_64-pc-linux-gnu)
On the above vesion of bash, the following script will not run the echo command
and print an error. On bash 4.4 it appears to treat the ${!foo} the same as
expanding an unset variable and thus outputs "bar":
unset foo
e
