After a little more experimentation, it appears that it only adds extra escape characters if mount (and unmount) are preceded by sudo. The only reason why umount worked for my test in my original message is because I didn't specify sudo. Adding sudo in front of other commands, such as cat and ls still works with tab completion, so it still seems to be limited to mount and umount.
On Sun, Oct 17, 2010 at 7:06 PM, Aaron Barany <akb...@gmail.com> wrote: > Package: mount > Version: 2.17.2-3.3 > Severity: minor > > Whenever you type the mount command in the terminal and tab-complete a > mount > point with spaces, extra escape characters are present. For example: > > mount /media/Shared\\\ Files > > Notice how there's 2 additional escape characters, which would cause mount > to > fail unless I go back and edit it, which removes the point of tab > completion. > Other commands, such as ls and even umount work properly, so that leads me > to > believe whatever configuration is set up for the tab completion is wrong > for > mount. > > > > -- System Information: > Debian Release: squeeze/sid > APT prefers testing > APT policy: (500, 'testing') > Architecture: amd64 (x86_64) > > Kernel: Linux 2.6.32-5-amd64 (SMP w/8 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 mount depends on: > ii libblkid1 2.17.2-3.3 block device id library > ii libc6 2.11.2-6 Embedded GNU C Library: Shared > lib > ii libselinux1 2.0.96-1 SELinux runtime shared > libraries > ii libsepol1 2.0.41-1 SELinux library for > manipulating b > ii libuuid1 2.17.2-3.3 Universally Unique ID library > > mount recommends no packages. > > Versions of packages mount suggests: > ii nfs-common 1:1.2.2-4 NFS support files common to > client > > -- no debconf information >
