GLOBIGNORE variable does not function when imported from environment, until it's modified

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

RE: bash 4.4 null byte warning!!

2017-04-09 Thread emlyn.j...@wipro.com
Hi Greg/Chet Ramey, Thank you so much for the response! It gave me an idea on what has to be done next. We have been using the same script all these years and had no issues of broken commands when used with the lower versions of bash which is why I have been thinking whether to rewrite the sc

Re: CTLESC and CTLNUL not dequoted in exported function definitions

2017-04-09 Thread Chet Ramey
On 4/9/17 6:12 PM, Grisha Levit wrote: > On Sun, Apr 9, 2017 at 5:56 PM, Chet Ramey wrote: >> Thanks for the report and fix. This is the patch where you could have used >> dequote_escapes() ;-) . > > Yup, I realized I'd done the previous one incorrectly shortly after writing > this one, sorry ab

extra field in $* expansion when non-whitespace character in IFS

2017-04-09 Thread Grisha Levit
In most cases, removing a non-whitespace IFS character "delimits" a field in the sense that it terminates it, so the presence of such a character at the end of a field does not change its expansion: $ IFS=X $ set -- Y; printf '<%s>' $* $ set -- YX; IFS=X; printf '<%s>' $* However, whe

Re: CTLESC and CTLNUL not dequoted in exported function definitions

2017-04-09 Thread Grisha Levit
On Sun, Apr 9, 2017 at 5:56 PM, Chet Ramey wrote: > Thanks for the report and fix. This is the patch where you could have used > dequote_escapes() ;-) . Yup, I realized I'd done the previous one incorrectly shortly after writing this one, sorry about that. But I'm not sure about dequoting the f

Re: CTLESC and CTLNUL not dequoted in exported function definitions

2017-04-09 Thread Chet Ramey
On 4/9/17 12:16 AM, Grisha Levit wrote: > f() { $'\001'; }; export -f f; printenv BASH_FUNC_f%% Thanks for the report and fix. This is the patch where you could have used dequote_escapes() ;-) . Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vi

Re: CTLESC and CTLNUL not dequoted in ${var@E}

2017-04-09 Thread Chet Ramey
On 4/8/17 11:26 PM, Grisha Levit wrote: > $ x='\001\177'; printf %q ${x@E} > $'\001\001\001\177' > > Probably just needs: > > --- a/subst.c > +++ b/subst.c > @@ -7253,7 +7253,7 @@ string_transform (xc, v, s) > break; >/* Transformations that modify the variable's value */ >