Re: Numbers in the begining of variable names generates problem

2013-10-11 Thread Eduardo A. Bustamante López
The error is very clear. ``2_ave'' is not a valid variable name. Use a valid name. This is not a bug, it is documented. Check the DEFINITIONS section of your bash manual, it says: name A word consisting only of alphanumeric characters and underscores, and beginning with an alpha

Numbers in the begining of variable names generates problem

2013-10-11 Thread Daniel Hagberg
Message-Id: Date: Fri, 11 Oct 2013 17:43:42 +0200 Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-linux-gnu' -DCON

Re: Bash 4.3 no longer handles traps when reading input with read

2013-10-11 Thread konsolebox
On Fri, Oct 11, 2013 at 10:06 PM, Chet Ramey wrote: The SIGCHLD handler was particularly bad, since children can die and interrupt the shell at any time. As an example, glibc uses internal locks extensively, especially within its malloc implementation, and running trap handlers w

Re: Bash 4.3 no longer handles traps when reading input with read

2013-10-11 Thread Chet Ramey
On 10/11/13 2:47 AM, konsolebox wrote: > Good day, > > It seems like starting 4.3 (beta2) bash already delays handling traps until > read exits. Is this intended? It would be a problem if read has a long > timeout or doesn't have a timeout at all: This is part of a significant rewrite of trap han