>>Maybe it changed between 5.3 rc2 and 5.3 release. 5.3 rc2 was compiled as
>>is; no
>>local changes.
>It didn't.
I could disprove this, but as I said before, it is not worth arguing about.
I'm surprised people are still posting about it.
===
On Mon, Sep 1, 2025, at 1:57 PM, Stan Marsh wrote:
>>>Maybe it changed between 5.3 rc2 and 5.3 release. 5.3 rc2 was compiled as
>>>is; no
>>>local changes.
>
>>It didn't.
>
> I could disprove this
% mkdir /tmp/bash && cd /tmp/bash
% curl -Os 'https://ftp.gn
On 8/31/25 10:51 AM, Stan Marsh wrote:
Maybe it changed between 5.3 rc2 and 5.3 release. 5.3 rc2 was compiled as is;
no
local changes.
It didn't.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU
On Mon, Sep 01, 2025 at 11:57:48 -0600, Stan Marsh wrote:
> >>Maybe it changed between 5.3 rc2 and 5.3 release. 5.3 rc2 was compiled as
> >>is; no
> >>local changes.
>
> >It didn't.
>
> I could disprove this, but as I said before, it is not worth arguing about.
> I'm surprised people are still
On 8/31/25 9:49 AM, Stan Marsh wrote:
But here's the thing: As far as I can tell, extglob is on-by-default - in all
the
versions of bash that I was able to test
It's not. You can configure bash to have it enabled by default
(--enable-extended-glob-default=yes) but it is not enabled by default
On 8/31/25 8:13 AM, pourko--- via Bug reports for the GNU Bourne Again
SHell wrote:
Aug 30, 2025, 12:08 by g...@wooledge.org:
All of these are compound commands, and must be parsed as a whole before
executing any of the simple commands contained inside them.
Sorry, Greg, but this is no "c
Maybe it changed between 5.3 rc2 and 5.3 release. 5.3 rc2 was compiled as is;
no
local changes.
Anyway, it is what it is. Doesn't matter. Not worth arguing about.
=
Please do not send me replies to my posts on the
On Sun, Aug 31, 2025 at 07:49:57 -0600, Stan Marsh wrote:
> But here's the thing: As far as I can tell, extglob is on-by-default - in all
> the
> versions of bash that I was able to test - so I don't understand why OP is
> messing
> around with turning it on and off. Or why Greg is talking about
On Aug 31 2025, Stan Marsh wrote:
> But here's the thing: As far as I can tell, extglob is on-by-default
No, it isn't.
$ bash -c 'shopt -p extglob'
shopt -u extglob
$ bash --version
GNU bash, version 5.3.3(1)-release (x86_64-suse-linux-gnu)
Copyright (C) 2025 Free Software Foundation, Inc.
Licen
On Sun, Aug 31, 2025 at 07:49:57AM -0600, Stan Marsh wrote:
> (>> == pourko, > == Greg)
>
> >> Sorry, Greg, but this is no "compound" command, these are separate
> >> commands:
> >>
> >> $ shopt -s extglob; echo !(this)
>
> >That is another case where it fails, correct.
>
> >However, in your o
(>> == pourko, > == Greg)
>> Sorry, Greg, but this is no "compound" command, these are separate commands:
>>
>> $ shopt -s extglob; echo !(this)
>That is another case where it fails, correct.
>However, in your original email, you did indeed have the shopt inside
>a compound command. That's why
On Sun, Aug 31, 2025 at 14:13:17 +0200, pou...@tutamail.com wrote:
> Aug 30, 2025, 12:08 by g...@wooledge.org:
>
> > All of these are compound commands, and must be parsed as a whole before
> > executing any of the simple commands contained inside them.
> >
>
> Sorry, Greg, but this is no "comp
Aug 30, 2025, 12:08 by g...@wooledge.org:
> This is the expected behavior.
>
I am actually disturbed by two problems here:
One is the brutal abort of the whole script on a "syntax error",
and the other is the suggestion that this...
$ shopt -s extglob; echo !(this)
...can behave differently t
Aug 30, 2025, 12:08 by g...@wooledge.org:
> All of these are compound commands, and must be parsed as a whole before
> executing any of the simple commands contained inside them.
>
Sorry, Greg, but this is no "compound" command, these are separate commands:
$ shopt -s extglob; echo !(this)
>
On Sat, Aug 30, 2025 at 15:07:10 +0200, pourko--- via Bug reports for the GNU
Bourne Again SHell wrote:
> After upgrading to bash-5.3, I ran into a strange problem with many of my
> scripts: It looks like in bash-5.3, setting the extglob option can crash my
> script, if the shopt command is inside
Greetings,
After upgrading to bash-5.3, I ran into a strange problem with many of my
scripts: It looks like in bash-5.3, setting the extglob option can crash my
script, if the shopt command is inside an if-then-fi structure, or if it's
inside a for-do-done loop. For example, here is a snippet t
16 matches
Mail list logo
