i like the currently showed behavior of '\' parsed as arg
no need to error .. if u meant that, ..
On Mon, Feb 14, 2022 at 11:17 PM Chet Ramey wrote:
> On 2/13/22 3:15 PM, vzvz...@gmail.com wrote:
>
> > Bash Version: 5.0
> > Patch Level: 17
> > Release Status: release
> >
> > Description:
> >
> >
On 2/13/22 3:15 PM, vzvz...@gmail.com wrote:
Bash Version: 5.0
Patch Level: 17
Release Status: release
Description:
Background
--
Commit a0c0a00fc419b7bc08202a79134fcd5bc0427071 (bash-4.4) introduced a change
in parse.y with following documentation in the change logs:
parse.y
vzvz...@gmail.com writes:
The mentioned bug is indeed fixed by this change. However, in case of
another edge case following new behaviour is observable:
$ bash -c 'echo \'
\
$ # backslash appears on output
It's an interesting case, since the command that Bash is executing is
e-c-h-o-sp
On 2/14/22 4:30 AM, Mihai Moldovan wrote:
Or maybe leaving shell_compatibility_level alone if it's > 44 (the last
compat_NN option) and <= DEFAULT_COMPATIBILITY_LEVEL (the current version)
instead of unconditionally setting it to DEFAULT_COMPATIBILITY_LEVEL. But
then you'd be required to unset B
* On 2/13/22 10:50 PM, Chet Ramey wrote:
> H. So what you're proposing is that `shopt -u compat43' if compat43 is
> not set should not reset the compatibility level to the current version.
> OK.
>
> I think we could do this by interrogating $BASH_COMPAT after unsetting the
> appropriate compat
