[Bug 1291169] Re: bash-completion behaves oddly under specific circumstances

Alberto Salvia Novella es20490446e at gmail.com
Sat Mar 22 14:43:06 UTC 2014


If you're still experiencing this bug, please set its status back to
"confirmed".

** Changed in: bash-completion (Ubuntu)
       Status: Confirmed => Fix Released

-- 
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/1291169

Title:
  bash-completion behaves oddly under specific circumstances

Status in “bash-completion” package in Ubuntu:
  Fix Released

Bug description:
  After some unknown update in the past at least week and a half or so,
  my bash completion has acted strangely:

  - if I begin a filename to complete with
      ~/
    I cannot complete filenames, only directory names, and the suggested names (if I press tab twice) show only directories (including hidden ones)
  - sometimes, under random circumstances, completing relative paths also has the above restrictions (most recently, trying to complete while in a subdirectory of /tmp exhibited this behavior)
  - if I start a command line as
      VAR= -l(space)
    for any VAR and -l and press tab, bash-complete throws up its "unknown argument/incorrect syntax" help message (in my case, I wanted to tab-complete an LDFLAGS=-L/... whose spaces would be removed once I found the directory that had the libraries)

  Everything else (completing absolute pathnames, command completion,
  etc.) works as expected. I do not have the /dir(space) tab-completion
  behavior that other questions about bash-complete found here and on
  Google cover.

  I tried removing /etc/bash_completion.d to no avail.
      sudo apt-get --reinstall install bash-complete
  did not work either.
      complete -r
  restores the intended behavior, so it is an issue with bash_completion... this has persisted across several updates to the bash-completion package as well (I am currently on 1:2.1-2ubuntu3).

  I am on Kubuntu 14.04 on a fresh install; this happens both in Konsole
  and in virtual terminals.

  What could be going on? Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: bash-completion 1:2.1-2ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Mar 11 23:43:32 2014
  InstallationDate: Installed on 2014-02-01 (38 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140121.1)
  PackageArchitecture: all
  SourcePackage: bash-completion
  UpgradeStatus: No upgrade log present (probably fresh install)

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



More information about the foundations-bugs mailing list