On Wed, 15 Feb 2023 12:48:10 +1000
Martin D Kealey wrote:
> > There are still Linux versions shipping with bash-4.2, which was released
> > in 2010.
> >
>
> Is anyone surprised by this, when new versions cannot be trusted?
It is, perhaps, telling that two of the most notable rolling Linux
On Tue, 14 Feb 2023 at 01:00, Chet Ramey wrote:
In this case, the behavior is controlled by an option. You just don't like
> the default setting.
> We had this exact same discussion back in November.
>
Too right I don't like it, and the previous discussion was wholly
unsatisfactory.
I do not
On 2/9/23 5:32 PM, Martin D Kealey wrote:
On 8 Feb 2023 at 18:50Z Tom Briden wrote:
Bash Version: 5.2
Patch Level: 15
Release Status: release
As of version 5.2-beta, replacing a single backslash with a double backslash is
no longer possible when using BASH_COMPAT=4.2.
On 9 Feb 2023 at
On Fri, 10 Feb 2023 11:32:54 +1300 (NZDT)
Martin D Kealey wrote:
> On 8 Feb 2023 at 18:50Z Tom Briden wrote:
> > Bash Version: 5.2
> > Patch Level: 15
> > Release Status: release
> >
> > As of version 5.2-beta, replacing a single backslash with a double
> > backslash is no longer possible when
On 8 Feb 2023 at 18:50Z Tom Briden wrote:
> Bash Version: 5.2
> Patch Level: 15
> Release Status: release
>
> As of version 5.2-beta, replacing a single backslash with a double backslash
> is no longer possible when using BASH_COMPAT=4.2.
On 9 Feb 2023 at 15:57Z Chet Ramey wrote:
> shopt -u
On 2/8/23 1:50 PM, Tom Briden via Bug reports for the GNU Bourne Again
SHell wrote:
Bash Version: 5.2
Patch Level: 15
Release Status: release
Description:
As of version 5.2-beta, replacing a single backslash with a double
backslash is no longer possible when using BASH_COMPAT=4.2.
The
