[Bug 1460165] Re: Bash completion of flags not working in Trusty

[Margarita Manterola]

The issue depends on the command and the flags.  For example, if I do:

marga at balerion:~$ pbuilder --basetgz=/var/<TAB>
backups/ crash/   local/   log/     metrics/ run/     tmp/     
cache/   lib/     lock/    mail/    opt/     spool/  

This works correctly, I guess because in the bash completion for this
command it's set that --basetgz wants path completion.

However, if I do:
marga at balerion:~$ pdebuild -- --basetgz=/var<TAB>

Nothing happens, because this is not specified in the bash completion.
Before, when a flag was not specified, it completed nonetheless, now if
it's not specified, it doesn't complete.  This puts a big burden on each
command providing the necessary bash completion in order to complete
paths with tabs which feels like the wrong way to go.

I can reproduce this also with the version in Debian testing
(1:2.1-4.2), so it's not confined to trusty.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to bash-completion in Ubuntu.
https://bugs.launchpad.net/bugs/1460165

Title:
  Bash completion of flags not working in Trusty

Status in bash-completion package in Ubuntu:
  Confirmed

Bug description:
  On the previous version of bash completion for Precise (bash-
  completion v1:1.3-1ubuntu8.1) I was able to use tab completion for
  filenames passed into commands as flags. In the current version in
  Trusty this functionality is missing.

  
  1. Release version: 
  Description:    Ubuntu 14.04.1 LTS
  Release:        14.04

  2. Package version:
  bash-completion 1:2.1-4

  3. What you expected to happen
  some_executable --file=/etc/h<TAB> should autocomplete to /etc/hosts

  4. What happened instead. 
  Tab completion does not work for filenames passed into commands as flags

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1460165/+subscriptions