Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: darwin20.5.0
Compiler: gcc
Compilation CFLAGS: -g -O2 -Wno-parentheses -Wno-format-security
uname output: Darwin Georges-Mac-Pro.local 20.5.0 Darwin Kernel Version
20.5.0: Sat May 8 05:10:33 PDT 2021; root:xnu-
Compilation CFLAGS: -g -O2 -Wno-parentheses -Wno-format-security
uname output: Linux bomb20 5.4.0-80-generic #90-Ubuntu SMP Fri Jul 9
22:49:44 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
Machine Type: x86_64-pc-linux-gnu
Bash Version: 5.1
Patch Level: 4
Release Status: maint
Description:
The
On Sat, 14 Aug 2021 15:59:38 -0700
George Nachman wrote:
> Configuration Information [Automatically generated, do not change]:
> Machine: x86_64
> OS: darwin20.5.0
> Compiler: gcc
> Compilation CFLAGS: -g -O2 -Wno-parentheses -Wno-format-security
> uname output: Darwin Georges-Mac-Pro.local 20.5.
On Sat, Aug 14, 2021, at 6:59 PM, George Nachman wrote:
> Description:
> Defining an alias named `done` breaks parsing a for loop that does not have
> an `in word` clause.
>
>
> Repeat-By:
>
> Run the following script. It fails with this error:
>
> myscript.bash: line 7: syntax error near unexp
On Sat, Aug 14, 2021, at 7:56 PM, Keith Thompson wrote:
> Bash Version: 5.1
> Patch Level: 4
> Release Status: maint
>
> Description:
> The builtin "printf" command with the "-v" option works
> correctly, but it reports failure by setting $? to 1.
>
> The problem was intro
Hi,
I was doing some testing for some additions to a rather big Bash script I'm
working on, and the following code kept failing whenever I attempted to run it:
"
variable="hello"
declare -g "${variable}"=("world" "me")
"
When run, it's complaining about a syntax error near "(", appea
On 8/13/21 2:01 PM, Léa Gris wrote:
> I would have really loved if Bash expanded translations with its
> built-in printf using a `-g` flag for gettext and positional arguments
> support instead of expanding string literal translations.
>
> It would have allowed something like :
>
> ```sh
> #!/usr
On Sun, Aug 15, 2021 at 1:59 AM George Nachman wrote:
> `done` should not be considered a simple command in the context where it
> would terminate a for loop. Alternately, prevent the user from creating
> aliases that will cause problems like this.
There already is an alias substitution rule for