On 6/24/21 5:44 AM, Koichi Murase wrote:
Maybe this is not caused by the change of this time, but another
related problem. When the nested command substitutions are incomplete,
an error message of the (false) syntax error is printed before PS2.
The command is still executed correctly after closin
On 6/24/21 5:18 AM, Koichi Murase wrote:
Please run it through any tests or scripts you have so we can shake out any
bugs early.
I haven't thoroughly tested it, but I found with a quick trial that
the parser state seems to remain broken in the new command line after
a syntax error:
Thanks for
Maybe this is not caused by the change of this time, but another
related problem. When the nested command substitutions are incomplete,
an error message of the (false) syntax error is printed before PS2.
The command is still executed correctly after closing the command
substitutions.
$ LANG=C ./ba
lol what the weird behavior
On Thu, Jun 24, 2021, 11:19 Koichi Murase wrote:
> > Please run it through any tests or scripts you have so we can shake out
> any
> > bugs early.
>
> I haven't thoroughly tested it, but I found with a quick trial that
> the parser state seems to remain broken in the
> Please run it through any tests or scripts you have so we can shake out any
> bugs early.
I haven't thoroughly tested it, but I found with a quick trial that
the parser state seems to remain broken in the new command line after
a syntax error:
$ ./bash --norc
$ printf '[%s]\n' $(if)
bash: synta
