[Bash-completion-devel] Bug#545743: bash-completion: sbcl completion and file/directory-name argument

[Christophe Rhodes]

Package: bash-completion
Version: 1:1.0-3
Severity: normal

Hi,

A common operation for me is to type
  ./sr<tab>ru<tab>sb<tab> --core ou<tab>sb<tab>
expecting that to complete to
  ./src/runtime/sbcl --core output/sbcl.core

Unfortunately, the <tab> after "ou" in that command line doesn't perform 
a partial complete to "output/", but (apparently) a full complete to 
"output ", meaning that I end up with a command-line of

  ./src/runtime/sbcl --core output sbcl-pwd.sh

(because "sbcl-pwd.sh" exists in the current directory).  This despite 
the fact that output/sbcl.core exists.  A similar effect can be seen 
simply doing
  sbcl --core /us<tab>
and trying to continue typing "lib" or similar.

I'm not sure when I would actually want this odd "treating directories 
as fully complete" behaviour, but I _definitely_ don't want it in this 
case.

Best wishes,

Christophe
-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.30-1-686 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages bash-completion depends on:
ii  bash                          3.2-6      The GNU Bourne Again SHell

bash-completion recommends no packages.

bash-completion suggests no packages.

-- no debconf information