Re: Conflicts between "complete" and "complete-filename"

[Chet Ramey]

On 5/22/10 2:07 PM, Henning Bekel wrote:
> Configuration Information [Automatically generated, do not change]:
> Machine: i686
> OS: linux-gnu
> Compiler: gcc
> Compilation CFLAGS:  -DPROGRAM='bash' -DCONF_HOSTTYPE='i686' -
> DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu' -
> DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash' -
> DSHELL -DHAVE_CONFIG_H   -I.  -I. -I./include -I./lib   -march=i686 -
> mtune=generic -O2 -pipe
> uname output: Linux box 2.6.33-ARCH #1 SMP PREEMPT Thu May 13 12:06:25 
> CEST 2010 i686 AMD Athlon(tm) XP 2200+ AuthenticAMD GNU/Linux
> Machine Type: i686-pc-linux-gnu
> 
> Bash Version: 4.1
> Patch Level: 7
> Release Status: release
> 
> Description: 
>       When the first word of the command line is a path containing
>       slashes and ending in a slash or a partial filename of a
>       non-executable file, if completion is attempted first via the
>       readline function "complete" and after that with
>       "complete-filename", then completion fails and
>       "complete-filename" behaves similar to "complete" in that it
>       only matches executable files and directories.

Thanks for the report.  complete-filename is not supposed to pay attention
to executable files when completing in a command position the way complete
does.  This will be fixed in the next release of bash.

Chet
-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
                 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU    chet@case.edu    http://cnswww.cns.cwru.edu/~chet/