Hello,
as reported in [286861], certain expressions may confuse bash so that it is no
longer able to evaluate assignments.
[286861] https://bugzilla.redhat.com/show_bug.cgi?id=286861
I tried to debug it and found that if evalerror (thus longjmp) is called while
noeval != 0, it stays nonzero and
"Chris F.A. Johnson" <[EMAIL PROTECTED]> writes:
>> $ let tmp="foo.a"+0
>> $ let ++i
>> $ echo $i
>> 0
>I agree that it is a bug, but it is one that will never bother me
>because I always use the POSIX arithmetic syntax:
happens there too:
$ : $(( tmp=foo.a+0 ))
bash: tmp=foo.a+0 : synta
On 2007-09-11, Enrico Scholz wrote:
> Configuration Information [Automatically generated, do not change]:
> Machine: i686
> OS: linux-gnu
> Compiler: gcc
> Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686'
> -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-redhat-linux-gnu'
> -DCONF_VEN
Configuration Information [Automatically generated, do not change]:
Machine: i686
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-redhat-linux-gnu'
-DCONF_VENDOR='redhat' -DLOCALEDIR='/usr/share/locale' -DPAC
