Re: . and .. are included where they were excluded before

On 27/01/2021 07:38, pepa65 wrote:
> On 27/01/2021 14.30, kfm@plushkava.net wrote:
> > Note that declare -p BASH_VERSION would report the version of bash that
> > you're currently running interactively.
>
> $ declare -p BASH_VERSION
> declare -- BASH_VERSION="5.0.17(1)-release"
>
> > Does declare -p GLOBIGNORE show that the variable is set? Does echo $-
> > show the letter 'f' anywhere?
>
> $ declare -p GLOBIGNORE
> declare -x GLOBIGNORE=".."

That's why your .? glob doesn't match the .. pathname. Normally, 
GLOBIGNORE isn't set.

> echo $-
> himBs
>
> No f, and GLOBIGNORE stays the same whether I do `shopt -s extglob` or
> `shopt -u extglob`... So probably ignore my results. But I would like to
> know what could be wrong with this system/install.

You may use the unset builtin to unset the GLOBIGNORE variable, or run 
bash with the --norc option to obtain the standard behaviour. I find it 
unlikely that Ubuntu would have chosen to interfere with this variable 
by default. At any rate, the following command may help you to track 
down where it's coming from.

$ PS4='+$BASH_SOURCE:$LINENO: ' bash -ixlc '' |& less

--
Kerin Millar