Re: avoid mktemp/mkstemp internally

On 19 May 2016 14:37, Chet Ramey wrote: > On 5/16/16 10:36 AM, Mike Frysinger wrote: > >> Because many traditional implementations of mktemp/mkstemp suck. > > > > and many modern implementations work perfectly fine. why is the default > > to penalize good/fixed versions ? how about we flip this

Re: Autocompletion problems with nounset and arrays

On 5/19/16 2:54 PM, Siteshwar Vashisht wrote: > > > - Original Message - >> From: "Chet Ramey" >> To: "Eric Pruitt" , bug-bash@gnu.org, >> b...@packages.debian.org >> Cc: "chet ramey" >> Sent: Tuesday, April 26, 2016 11:24:12 PM >> Subject: Re: Autocompletion problems with nounset and

Re: Autocompletion problems with nounset and arrays

- Original Message - > From: "Chet Ramey" > To: "Eric Pruitt" , bug-bash@gnu.org, > b...@packages.debian.org > Cc: "chet ramey" > Sent: Tuesday, April 26, 2016 11:24:12 PM > Subject: Re: Autocompletion problems with nounset and arrays > > Thanks for the report. I will fix this before

Re: avoid mktemp/mkstemp internally

On 5/16/16 10:36 AM, Mike Frysinger wrote: >> Because many traditional implementations of mktemp/mkstemp suck. > > and many modern implementations work perfectly fine. why is the default > to penalize good/fixed versions ? how about we flip this in config-top.h > like the attached patch ? Yes,

Re: coproc and existing variables

On 5/17/16 5:03 PM, Grisha Levit wrote: > On Mon, May 16, 2016 at 4:44 PM, Grisha Levit > wrote: > > * The %s_PID variable is unbound unconditionally > > BTW, this is exploitable for unsetting read-only variables. Same change as for getopts. -- ``The lyf so

Re: coproc and existing variables

On 5/17/16 5:14 PM, Grisha Levit wrote: > On Sun, Apr 24, 2016 at 2:17 PM, Chet Ramey > wrote: > > it seems reasonable to follow printf/read/mapfile and not overwrite read- > only variables used as coproc names. getopts will remain an outlier. > > getopts can