Re: bash crashes when the REPLY variable is read only and the 'select' builtin is used.

2015-01-14 Thread Chet Ramey
On 1/14/15 1:10 PM, Etherial Raine wrote: > Bash Version: 4.3 > Patch Level: 11 > Release Status: release > > Description: > Using select after making the variable 'REPLY' readonly via > 'readonly REPLY', bash will crash. > > Repeat-By: > > - snapshot starts - > > gab

Re: Tab completion breaks for tilde-paths with filenames containing space

2015-01-14 Thread Chet Ramey
On 1/14/15 10:52 AM, Dave Rutherford wrote: > On Wed, Jan 14, 2015 at 10:14 AM, Eduardo A. Bustamante López > wrote: >> Can you test with: >> bash --norc --noprofile -i > > It is working in this case. The difference seems to be in direxpand. Thanks, that was the key. This will be fixed in the

bash crashes when the REPLY variable is read only and the 'select' builtin is used.

2015-01-14 Thread Etherial Raine
Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-linux-gnu' -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKA

Re: [Bug-readline] incorrect "erase" of multibyte characters in "reverse-i-search" mode.

2015-01-14 Thread Chet Ramey
On 1/13/15 6:05 AM, Kyrylo Shpytsya wrote: > readline version: 6.3_p8 and the one in devel branch of bash > OS: gentoo linux "unstable", kernel 3.17, UTF-8 locale > To reproduce: > > in bash, press Ctrl-R to invoke reverse-i-search mode, enter any multi-byte > character (on US keyboard layout LAlt

Re: Tab completion breaks for tilde-paths with filenames containing space

2015-01-14 Thread Dave Rutherford
On Wed, Jan 14, 2015 at 10:14 AM, Eduardo A. Bustamante López wrote: > Can you test with: > bash --norc --noprofile -i It is working in this case. The difference seems to be in direxpand. $ shopt -s direxpand; shopt direxpand direxpand on $ vi ~/a/a\ [nothing] $ shopt -u direxpand

Re: Tab completion breaks for tilde-paths with filenames containing space

2015-01-14 Thread Andreas Schwab
Dave Rutherford writes: > On Wed, Jan 14, 2015 at 9:45 AM, Eduardo A. Bustamante López > wrote: >> Are you using any supplementary programs, like bash-completion? > > I don't think so, unless Debian turned it on for me. Run complete -p to find out. Andreas. -- Andreas Schwab, SUSE Labs, sch.

Re: Tab completion breaks for tilde-paths with filenames containing space

2015-01-14 Thread Chet Ramey
On 1/14/15 9:33 AM, d...@evilpettingzoo.com wrote: > Bash Version: 4.2 > Patch Level: 37 > Release Status: release > > Description: > Pathnames starting with tilde, combined with filenames containing > space, only partially tab-complete. I can't reproduce this using bash-4.2.53 or bash-4.

Re: CHLD traps run at the same time

2015-01-14 Thread Chet Ramey
On 1/14/15 6:01 AM, Øyvind 'bolt' Hvidsten wrote: > I'm responsible for a couple of scripts at work, which have used a trap on > CHLD to do some naive parallelisation, starting a new child process when an > existing one ends. > > However, when run under bash 4.3.30, all CHLD traps run at the same

Re: Tab completion breaks for tilde-paths with filenames containing space

2015-01-14 Thread Eduardo A . Bustamante López
On Wed, Jan 14, 2015 at 09:55:33AM -0500, Dave Rutherford wrote: [...] > I don't think so, unless Debian turned it on for me. Can you test with: bash --norc --noprofile -i > Note that without a\ a.odt there, > $ ls ~/a/a[completes to a\ a.txt] > but > $ ls ~/a/a\ [do

Re: Tilde expansion differences between 4.3 and 4.2

2015-01-14 Thread Chet Ramey
On 1/14/15 9:09 AM, Ondrej Oprala wrote: > reproducer: > cd ~ > mkdir MYDIR > cd MYDIR > echo "${PWD/#$HOME/~}" > > Result of echo in 4.3: > /home//MYDIR > > Result of echo in 4.2: > ~/MYDIR > > Is tilde expansion in 4.3 supposed to happen? Yes. It's a Posix change. Look at http://austingrou

Re: Tab completion breaks for tilde-paths with filenames containing space

2015-01-14 Thread Dave Rutherford
On Wed, Jan 14, 2015 at 9:45 AM, Eduardo A. Bustamante López wrote: > On Wed, Jan 14, 2015 at 09:33:31AM -0500, d...@evilpettingzoo.com wrote: > [...] >> Bash Version: 4.2 >> Patch Level: 37 Also tested on 4.3.30 > [dualbus@dualbus ~]$ mkdir a; >a/a\ a.txt You didn't create any ambiguity there.

Re: Tab completion breaks for tilde-paths with filenames containing space

2015-01-14 Thread Eduardo A . Bustamante López
On Wed, Jan 14, 2015 at 09:33:31AM -0500, d...@evilpettingzoo.com wrote: [...] > Bash Version: 4.2 > Patch Level: 37 [dualbus@dualbus ~]$ mkdir a; >a/a\ a.txt [dualbus@dualbus ~]$ echo ~/a/a [completes] [dualbus@dualbus ~]$ echo ~/a/a\ a.txt /home/dualbus/a/a a.txt [dualbus@dualbus ~]$ echo ~/a/a\

Re: Tilde expansion differences between 4.3 and 4.2

2015-01-14 Thread Eduardo A . Bustamante López
See: - http://lists.gnu.org/archive/html/bug-bash/2014-10/msg00200.html - http://lists.gnu.org/archive/html/bug-bash/2014-04/msg00077.html - http://lists.gnu.org/archive/html/bug-bash/2014-10/msg00202.html

Tab completion breaks for tilde-paths with filenames containing space

2015-01-14 Thread dave
Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-linux-gnu' -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKA

Re: Tilde expansion differences between 4.3 and 4.2

2015-01-14 Thread Greg Wooledge
On Wed, Jan 14, 2015 at 03:09:47PM +0100, Ondrej Oprala wrote: > echo "${PWD/#$HOME/~}" > > Result of echo in 4.3: > /home//MYDIR imadev:~/tmp$ echo "$BASH_VERSION -- ${PWD/#$HOME/\~}" 4.3.30(5)-release -- ~/tmp imadev:~/tmp$ bash-4.2 -c 'echo "$BASH_VERSION -- ${PWD/#$HOME/\~}"' 4.2.46(1)-relea

Tilde expansion differences between 4.3 and 4.2

2015-01-14 Thread Ondrej Oprala
reproducer: cd ~ mkdir MYDIR cd MYDIR echo "${PWD/#$HOME/~}" Result of echo in 4.3: /home//MYDIR Result of echo in 4.2: ~/MYDIR Is tilde expansion in 4.3 supposed to happen? I don't see any mention in 4.3's compat file, apart from point 20 which was already present in COMPAT files for older v

Re: Nested calls to getopts incorrectly parses clustered options

2015-01-14 Thread Chet Ramey
On 1/14/15 5:35 AM, Øyvind 'bolt' Hvidsten wrote: > Nobody else having issues with this? > It's still a case in bash 4.3.30 There is a change in the devel branch that makes local copies of OPTIND behave as you expect. -- ``The lyf so short, the craft so long to lerne.'' - Chaucer

CHLD traps run at the same time

2015-01-14 Thread Øyvind 'bolt' Hvidsten
I'm responsible for a couple of scripts at work, which have used a trap on CHLD to do some naive parallelisation, starting a new child process when an existing one ends. However, when run under bash 4.3.30, all CHLD traps run at the same time, so my script runs in chunks, rather than keeping a

Re: Nested calls to getopts incorrectly parses clustered options

2015-01-14 Thread Pierre Gaston
On Wed, Jan 14, 2015 at 12:35 PM, Øyvind 'bolt' Hvidsten wrote: > Nobody else having issues with this? > It's still a case in bash 4.3.30 > > > On 31/05/14 18:40, Øyvind Hvidsten wrote: > >> For a simple test: >> >> $ f() { local OPTIND=1 OPTARG OPTERR opt; while getopts ":abcxyz" opt; >> do echo

Re: Nested calls to getopts incorrectly parses clustered options

2015-01-14 Thread Øyvind 'bolt' Hvidsten
Nobody else having issues with this? It's still a case in bash 4.3.30 On 31/05/14 18:40, Øyvind Hvidsten wrote: For a simple test: $ f() { local OPTIND=1 OPTARG OPTERR opt; while getopts ":abcxyz" opt; do echo "opt: $opt"; if [[ "$opt" = "y" ]]; then f -a -b -c; fi; done; }; f -x -y -z opt: x o