${!prefix@} no longer expands in Bash 4.4-alpha

2015-07-11 Thread konsolebox
Bash 4.4-alpha no longer expands ${!prefix@}. ${!prefix*} however still works. bash-4.4-alpha-4.4# var_1=a var_2=b bash-4.4-alpha-4.4# set -- ${!var_@} bash-4.4-alpha-4.4# echo $# 0 bash-4.4-alpha-4.4# set -- "${!var_@}" bash-4.4-alpha-4.4# echo $# 1 bash-4.4-alpha-4.4# set -- ${!var_*} bash-4.4-a

problem with HISTCONTROL

2015-07-11 Thread isabella parakiss
When the value of HISTCONTROL is ignoredups or ignoreboth, if you enter a command and then open the editor and add lines to it without changing the first line, only the first line will be stored in the history. I'm terrible at explaining, but I recorded what happens: https://asciinema.org/a/23275

Re: address XXX comment at lines 987-990 in bashfile.c

2015-07-11 Thread Bill Parker
The comment above the line would seem to indicate otherwise: Here is the comment: /* Now erase the contents of the current line and undo the effects of the rl_accept_line() above. We don't even want to make the text we just executed available for undoing. */ Bill On Fri, Jul 10,

Re: bash-4.3 stack smashing

2015-07-11 Thread Chet Ramey
On 7/9/15 5:44 AM, Ondrej Oprala wrote: > Hi, > devel branch's commit 67440b introduced a change in sig.c; specifically, > deleting line 608 > seems to solve the problem (though I've no idea what else it breaks). Thanks for the report and the pointer to the place to investigate. This will be fixe

Re: address XXX comment at lines 987-990 in bashfile.c

2015-07-11 Thread Chet Ramey
On 7/11/15 4:15 PM, Bill Parker wrote: > The comment above the line would seem to indicate otherwise: > > Here is the comment: > >/* Now erase the contents of the current line and undo the effects of the > rl_accept_line() above. We don't even want to make the text we just > exec

Re: ${!prefix@} no longer expands in Bash 4.4-alpha

2015-07-11 Thread Chet Ramey
On 7/11/15 12:17 PM, konsolebox wrote: > Bash 4.4-alpha no longer expands ${!prefix@}. > ${!prefix*} however still works. Yeah, it was a bad idea to make ${!prefix@} ever work in the first place. The original intent was to use ${!prefix*} like in ksh93, but * and @ are the same just about everywhe

Re: Troubles with autocompletion of filenames with square brackets

2015-07-11 Thread Chet Ramey
On 7/10/15 3:36 AM, deterenkelt.git...@gmail.com wrote: > Bash Version: 4.3 > Patch Level: 39 > Release Status: release > > Description: > Autocompletion fails for files starting with an opening square bracket > and having closing bracket somewhere in the filename. I can't reproduce this

Re: Troubles with autocompletion of filenames with square brackets

2015-07-11 Thread deterenkelt
Thanks, now the completion works fine, I’ll send a bug to maintainers. 2015-07-12 4:34 GMT+03:00 Chet Ramey : > On 7/10/15 3:36 AM, deterenkelt.git...@gmail.com wrote: > > > Bash Version: 4.3 > > Patch Level: 39 > > Release Status: release > > > > Description: > > Autocompletion fails for f