On Fri, Oct 13, 2023 at 5:59 PM Grisha Levit wrote:
> On Fri, Oct 13, 2023, 10:03 Ti Strga wrote:
>>
>> [*] Alternatively, there's the trick about putting the entire script
>> contents inside a compound statement to force the parser to read it all,
>> but that j
On Fri, Oct 13, 2023 at 5:35 PM Chet Ramey wrote:
> This is what happens. First, you have to remember that variables supplied
> as temporary assignments to builtins like eval and source persist for the
> entire life of that builtin's execution, and appear in the environment of
> child processes
On Fri, Oct 13, 2023 at 2:22 PM Dale R. Worley wrote:
> $ bash -version
> GNU bash, version 5.1.0(1)-release (x86_64-redhat-linux-gnu)
If I can get 5.1.x installed, I'll try with that; if the behavior is no longer
exhibited then it's possible something got wonky between then and
5.2.15.
First off, I have a feeling that GMail is going to garble the line
wrapping in this message; I cannot get it to stop being "helpful".
Apologies if that happens.
I've encountered some behavior that I cannot find described anywhere in
the man page, and I'm hoping to learn whether it's a bug (it
The bug likely got checked in earlier than 5.2.15, that's just what I
happened to be running when I ran into this.
$ declare -p BASH_VERSINFO
declare -ar BASH_VERSINFO=([0]="5" [1]="2" [2]="15" [3]="3"
[4]="release" [5]="x86_64-pc-cygwin")
$ bashbug
/usr/bin/bashbug: line 135: [: missing `]'
