Bug#814570: debdiff: Bash completion on a filename parameter fails if a leading directory specified

[Ben Finney]

Control: found -1 devscripts/2.16.4
Control: owner -1 !
Control: retitle -1 debdiff: Bash completion on a filename parameter fails if a leading directory specified

On 13-Feb-2016, Salvatore Bonaccorso wrote:

> Recently (I think since 2.15.10 where bash completions were
> reorganized), debdiff cannot bash complete anymore to files if they
> are not in the current directory.

The test case is even simpler: specify a path with *any* directory,
even the current (‘.’) directory, leading the path.

    $ ls -l *.deb
    foo_1.2.3-1_all.deb

    $ debdiff foo<TAB>    # result: completes the package name.

    $ debdiff ./foo<TAB>  # result: no completion found.

I will attempt fixing this.

-- 
 \                  “The shortest distance between two points is under |
  `\                                      construction.” —Noelie Alito |
_o__)                                                                  |
Ben Finney <ben at benfinney.id.au>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/devscripts-devel/attachments/20160514/d0ec6a26/attachment-0001.sig>