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

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

CTLESC and CTLNUL not dequoted in exported function definitions

2017-04-08 Thread Grisha Levit
For example: $ f() { $'\001'; }; export -f f; printenv BASH_FUNC_f%% | xxd : 2829 207b 2020 2701 0127 0a7d 0a () { '..'.}. I think the following should fix it: diff --git a/variables.c b/variables.c index 87203dac..acac867e 100644 --- a/variables.c +++ b/variables.c @@ -4309,7 +