Package: bash-completion Version: 1:1.3-1 Severity: minor Path completion has strage behaviour after the recent upgrade on my box.
Take the command `ls' as an example. Notice, I add a '#' at each command line just to show the end of line, the '#' is not typed. Before the upgrade, $ ls /var<TAB><TAB># gives $ ls /var/# backups/ games/ local/ log/ opt/ spool/ www/ cache/ lib/ lock/ mail/ run/ tmp/ the subdirs are list as completion. But now, $ ls /var<TAB><TAB># gives $ ls /var # and "/var " is treated as a complete argument, if you press <TAB><TAB> again, it begins a new completion (list subdirs in current dir), but not to list subdirs in /var/. Not only `ls', there are quite a lot of commands behave like this, `cp', `mv', `tar', `rm' (rm with this strage behaviour is quite dangerous).... There are still some commands dosen't have this problem, like `cd', `svn'.... -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-trunk-686 (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. -- no debconf information _______________________________________________ Bash-completion-devel mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
