Re: bashbug chooses wrong $EDITOR executable

Chet Ramey wrote: > Bob Proulx wrote: > > It seems okay to leave PATH alone to me. Why set it at all? > > > > I don't see the security issue that you are concerned about. Could > > you educate me? > > I suppose it's not a large security hole if $EDITOR is used, only > when bashbug chooses $DEFE

Re: Possible Bug in BASH

Matthew Strax-Haber wrote: > I think I may have found a bug in BASH 3.2.17(1)-release on a mac. I am not sure it is a bug but it does seem ood. > Below is a simple demonstration of the unexpected behavior: > > SHELL 1: > mattsh$ alias c=clear > mattsh$ c () { echo foo; } > mattsh$ clear > foo He

Possible Bug in BASH

I think I may have found a bug in BASH 3.2.17(1)-release on a mac. Below is a simple demonstration of the unexpected behavior: SHELL 1: mattsh$ alias c=clear mattsh$ c () { echo foo; } mattsh$ clear foo SHELL 2: mattsh$ alias c=clear mattsh$ function c () { echo foo; } mattsh$ clear [blanks scre

cannot catch returncode if assigning local variables in functions

Configuration Information [Automatically generated, do not change]: Machine: i486 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i486' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i486-pc-linux-gnu' -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='ba

bash 4.0 on Interix (struct timezone/allsource and broken_dirent_d_no/missing includes)

/src/bash-4.0/execute_cmd.c: In function `time_command': /src/bash-4.0/execute_cmd.c:1145: error: storage size of `dtz' isn't known make: *** [execute_cmd.o] Error 1 /usr/include/sys/time.h: #if defined(_ALL_SOURCE) /* * historical structure for use in 2nd paramter of gettimeofday(). * N

Re: printf has weird behaviour when parsing zero padded numbers

On Jun 19, 6:58 pm, bitozoid wrote: > Configuration Information [Automatically generated, do not change]: > Machine: i686 > OS: linux-gnu > Compiler: i686-pc-linux-gnu-gcc > Compilation CFLAGS:  -DPROGRAM='bash' -DCONF_HOSTTYPE='i686' - > DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu

printf has weird behaviour when parsing zero padded numbers

Configuration Information [Automatically generated, do not change]: Machine: i686 OS: linux-gnu Compiler: i686-pc-linux-gnu-gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686' - DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu' - DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/loc