Debian Bug report logs - #590131
bash-completion: No longer completes fusermount -u in certain cases

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Francis Russell <francis+dbts@unchartedbackwaters.co.uk>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: bash-completion: No longer completes fusermount -u in certain cases

Date: Sat, 24 Jul 2010 01:27:22 +0100

Package: bash-completion
Version: 1:1.2-2
Severity: normal


fusermount is a tool used to mount/unmount FUSE filesystems.  To unmount a fuse
filesystem, one invokes:

fusermount -u mountpoint

It is no longer possible to tab-complete the mount-point when the mount point
begins with '~', uses a relative path or any other type of expansion. Instead I'm
forced to use to entire path. This wasn't an issue with earlier
bash-completion versions, though it's possible the fuse auto-completion stuff wasn't
specifically trying to match paths from /etc/mtab.


-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing'), (50, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.34.1 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

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

Message #14 received at 590131-close@bugs.debian.org (full text, mbox, reply):

From: "Gabriel F. T. Gomes" <gabriel@inconstante.net.br>

To: <590131-close@bugs.debian.org>

Subject: Re: bash-completion: No longer completes fusermount -u in certain cases

Date: Sun, 2 Dec 2018 21:59:48 -0200

On Sat, 24 Jul 2010 01:27:22 +0100 Francis Russell <francis+dbts@unchartedbackwaters.co.uk> wrote:
> 
> fusermount is a tool used to mount/unmount FUSE filesystems.  To unmount a fuse
> filesystem, one invokes:
> 
> fusermount -u mountpoint
> 
> It is no longer possible to tab-complete the mount-point when the mount point
> begins with '~', uses a relative path or any other type of expansion. Instead I'm
> forced to use to entire path. This wasn't an issue with earlier
> bash-completion versions, though it's possible the fuse auto-completion stuff wasn't
> specifically trying to match paths from /etc/mtab.

The old behaviour, which can be reproduced by using the older
completion file for fusermount [1], had no special treatment of
mountpoints and was suggesting regular file and directory completions.
The new behaviour tries to be smarter in the suggestions.

If you want the old behavior, you can use Alt+/, which is the default
bash shortcut for "complete on all files".

I'm closing this bug, but please do not hesitate to reopen it if you
disagree with the solution.

Thanks,
Gabriel


[1] https://github.com/scop/bash-completion/blob/f8a2d6778339f344460ab86bf4bbe6235e88ccec/contrib/fuse
(to reproduce, copy it over to /usr/share/bash-completion/completions/fusermount)

Send a report that this bug log contains spam.