Re: Fwd: Problem with bash completion

[Chris F.A. Johnson]

On 2008-03-13, Eric Blake wrote:
>
> This was originally reported on the cygwin lists; it is still present in
> stock bash 3.2.33.
>
> - -----
>
> From: David Rothenberger
> Subject: Problem with bash completion
>
> Sometimes bash gets confused and starts adding a slash at the end of
> files when I do tab-completion. Here's a simple reproduction script:
>
> ~ > bash --noprofile --norc -i
> bash-3.2$ mkdir /tmp/bash-problem
> bash-3.2$ cd /tmp/bash-problem
> bash-3.2$ mkdir d
> bash-3.2$ touch x
> bash-3.2$ chmod 755 x
> bash-3.2$ ./x                <---- tab after x completes correctly
> bash-3.2$ ./d/               <---- ditto with d
> bash: ./d/: is a directory
> bash-3.2$ "$(ls ./d/)"       <---- pressed tab after d
> bash: : command not found
> bash-3.2$ ./x/               <---- tab after x now adds slash
>
> Once the shell starts doing this, it keeps doing it. Restarting bash
> solves the problem.

       I don't see that problem, and I'm using the same version of
       bash.

-- 
   Chris F.A. Johnson, webmaster         <http://Woodbine-Gerrard.com>
   ===================================================================
   Author:
   Shell Scripting Recipes: A Problem-Solution Approach (2005, Apress)
.