Re: Setting nullglob causes variables containing backslashes to be expanded to an empty string

From	Stephane Chazelas <stephane.chazelas@gmail.com>
Newsgroups	gnu.bash.bug
Subject	Re: Setting nullglob causes variables containing backslashes to be expanded to an empty string
Date	2019-08-06 21:42 +0100
Organization	A noiseless patient Spider
Message-ID	<20190806204248.lbe57vapurinrh5b@chaz.gmail.com> (permalink)
References	<5202404D-4B1E-4627-9FDE-2E0C5608A5B7@outlook.com> <20190806200021.GK1218@eeg.ccf.org> <mailman.968.1565121631.1985.bug-bash@gnu.org> <20190806202819.3zpyixfptmqrdvgr@chaz.gmail.com> <20190806203955.nba45vjkmx5bu2a6@chaz.gmail.com>

Show all headers | View raw

2019-08-06 21:39:55 +0100, Stephane Chazelas:
[...]
> with the current head of the  devel branch, that behaviour can
> be disabled by turning off the posixglob option (I still do hope
> that POSIX will give up on this silly idea).
> 
> $ a='\x30' ./bash +O posixglob -O nullglob -c 'printf "%s\n" $a'
> \x30
> $ a='\x30' ./bash -O nullglob -c 'printf "%s\n" $a'
> 

Sorry, there was a missing

$ touch x30

there.

> $ a='\x30' ./bash -O nullglob -c 'printf "%s\n" $a'
> x30

Back to gnu.bash.bug | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Re: Setting nullglob causes variables containing backslashes to be expanded to an empty string Greg Wooledge <wooledg@eeg.ccf.org> - 2019-08-06 16:00 -0400
  Re: Setting nullglob causes variables containing backslashes to be expanded to an empty string Stephane Chazelas <stephane.chazelas@gmail.com> - 2019-08-06 21:28 +0100
    Re: Setting nullglob causes variables containing backslashes to be expanded to an empty string Stephane Chazelas <stephane.chazelas@gmail.com> - 2019-08-06 21:39 +0100
      Re: Setting nullglob causes variables containing backslashes to be expanded to an empty string Stephane Chazelas <stephane.chazelas@gmail.com> - 2019-08-06 21:42 +0100

csiph-web