Re: Change in behavior

2016-12-13 Thread Vladimir Marek
> >> Posix says a word expansion error shall cause a non-interactive shell to > >> exit: > >> > >> http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_08_01 > >> > >> Bash posix mode changed as the result of this report: > >> > >>

Re: Change in behavior

2016-12-13 Thread Chet Ramey
On 12/13/16 10:37 AM, Vladimir Marek wrote: >> Posix says a word expansion error shall cause a non-interactive shell to >> exit: >> >> http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_08_01 >> >> Bash posix mode changed as the result of this report: >> >>

Re: Change in behavior

2016-12-13 Thread Vladimir Marek
> Posix says a word expansion error shall cause a non-interactive shell to > exit: > > http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_08_01 > > Bash posix mode changed as the result of this report: > >

Re: Change in behavior

2016-12-13 Thread Chet Ramey
On 12/13/16 10:08 AM, Vladimir Marek wrote: > Hi, > > by coincidence I found change in behavior in how bash treats syntax > error. Can you see the difference on your machines too? > > $ cat configure > set -o posix > echo ${0.8} > echo after > > $ bash a.sh > 3.2.52(1)-release > a.sh: line 3:

Re: Change in behavior

2016-12-13 Thread Greg Wooledge
On Tue, Dec 13, 2016 at 09:16:12AM -0600, Eduardo Bustamante wrote: > On Tue, Dec 13, 2016 at 9:08 AM, Vladimir Marek > wrote: > [...] > > $ cat configure > > set -o posix > > echo ${0.8} > > echo after > > > > $ bash a.sh > > 3.2.52(1)-release > > a.sh: line 3: ${0.8}:

Re: Change in behavior

2016-12-13 Thread Vladimir Marek
> > $ cat configure > > set -o posix > > echo ${0.8} > > echo after > > > > $ bash a.sh > > 3.2.52(1)-release > > a.sh: line 3: ${0.8}: bad substitution > > after > Is `a.sh' a copy of `configure'? Oh, yes, sorry, it's the same file. It's a part of libvisual-plugins's configure script. --

Re: Change in behavior

2016-12-13 Thread Eduardo Bustamante
On Tue, Dec 13, 2016 at 9:08 AM, Vladimir Marek wrote: [...] > $ cat configure > set -o posix > echo ${0.8} > echo after > > $ bash a.sh > 3.2.52(1)-release > a.sh: line 3: ${0.8}: bad substitution > after Is `a.sh' a copy of `configure'?

Re: change in behavior starting with bash-4.3_p14 and $@ in [[...]]

2014-08-13 Thread Chet Ramey
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 8/12/14, 11:05 PM, Mike Frysinger wrote: simple enough code: foo=(0 0 0); [[ -z ${foo[@]#0} ]]; echo $? with bash-4.3_p13 and older, this would show 0. starting with bash-4.3_p14, this now shows 1. It's intentional, and part of the same

Re: change in behavior starting with bash-4.3_p14 and $@ in [[...]]

2014-08-13 Thread Greg Wooledge
On Wed, Aug 13, 2014 at 09:47:51AM -0400, Chet Ramey wrote: On 8/12/14, 11:05 PM, Mike Frysinger wrote: foo=(0 0 0); [[ -z ${foo[@]#0} ]]; echo $? Word splitting is suppressed inside [[, so the array expands to a single word (0 0 0), the 0s are removed, leaving That doesn't sound right.

Re: change in behavior starting with bash-4.3_p14 and $@ in [[...]]

2014-08-13 Thread Chet Ramey
On 8/13/14, 10:09 AM, Greg Wooledge wrote: On Wed, Aug 13, 2014 at 09:47:51AM -0400, Chet Ramey wrote: On 8/12/14, 11:05 PM, Mike Frysinger wrote: foo=(0 0 0); [[ -z ${foo[@]#0} ]]; echo $? Word splitting is suppressed inside [[, so the array expands to a single word (0 0 0), the 0s are