Re: SEGV on unbounded recursion

2008-03-08 Thread Chet Ramey
[EMAIL PROTECTED] 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_VENDOR='redhat' -DLOCALEDI

Re: style of assignment to variable changes command selection

2008-03-08 Thread Chet Ramey
Eric Blake wrote: Re-adding the list - I am not the bash maintainer, so keeping the list in the loop is essential if you want any action taken. I am the bash maintainer, so I figure my opinion will count for something. | So there's a bug in the manual, which does not breathe a word about | ti

Re: style of assignment to variable changes command selection

2008-03-08 Thread Chet Ramey
Doug McIlroy wrote: These two bash sequences are not equivalent. My intuition and the bash man page tell me they should be the same. % export X=x; time --version; unset X -bash: --version: command not found % unset X; X=x time --version GNU time 1.7 They are not the same, and should n

Re: style of assignment to variable changes command selection

2008-03-08 Thread Jan Schampera
Bob Proulx wrote: > This implies to me that a variable assignment forces subsequent > commands to be external commands because the current environment is > not affected. In your case above the external /usr/bin/time program > is forced by the variable assignment requiring the environment > variab