> >> 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:
> >>
> >> http://lists.gnu.org/archive/html/bug-ba
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:
>>
>> http://lists
> 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:
>
> http://lists.gnu.org/archive/html/bug-bash/2015-08/msg00013.h
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: ${
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}: bad substitution
> > after
> > $ 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.
--
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'?
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: ${0.8}: bad substitution
after
$ bash a.sh
4.3.46(1)-release
build/i86/
