[Bash-completion-devel] Bug#630521: bash-completion: no longer completes files for vi
Michal Suchanek
hramrach at centrum.cz
Tue Jun 14 19:05:07 UTC 2011
Package: bash-completion
Version: 1:1.3-3
Severity: important
This is a regression, it used to be possible to complete pretty much any
file. Now only directories are completed for vi, or some very unusual
files I don't have.
To fix this I had to comment out the line
complete -f -X
'*.@(o|so|so.!(conf)|a|[rs]pm|gif|jp?(e)g|mp6|mp?(e)g|avi|asf|ogg|class)'
vi vim gvim rvim view rview rgvim rgview gview emacs xemacs sxemacs kate
kwrite
I am not sure what it is supposed to do but it definitely breaks editor
completion making them totally unusable from bash.
-- System Information:
Debian Release: wheezy/sid
APT prefers stable
APT policy: (990, 'stable'), (500, 'testing'), (400, 'unstable'), (395, 'experimental'), (300, 'stable-i386'), (300, 'oldstable'), (280, 'testing-i386'), (270, 'unstable-i386'), (150, 'experimental-i386'), (65, 'oldstable-i386')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.39-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages bash-completion depends on:
ii bash 4.1-3 The GNU Bourne Again SHell
bash-completion recommends no packages.
bash-completion suggests no packages.
-- debconf-show failed
-- debsums errors found:
debsums: changed file /usr/share/bash-completion/bash_completion (from bash-completion package)
More information about the Bash-completion-devel
mailing list