[Bash-completion-devel] mount, umount completions
Raphaël
raphael.droz+floss at gmail.com
Sun Dec 4 17:49:07 UTC 2011
On Sun, Dec 04, 2011 at 05:58:27PM +0400, Igor Murzov wrote:
> > > But I've *guessed* something else:
> > >
> > > $ umount <tab>
> > > # list the entries including /home/me/private
> > > $ cd /home/me
> > > $ umount pri<tab>
> > > # list pri* with filedir -d instead of "private" only
> >
> > I've tried to fix this: http://anonscm.debian.org/gitweb/?p=bash-completion/bash-completion.git;a=commit;h=7a1a3da08a77de2952b75dc514fa962d874c5c95
> > This is not a real fix, you still won't be able to do something like:
> >
> > $ umount ../mountpoint
> >
> > but umount should work for current directory now. Real fix requires somewhat intrusive changes and I'm not sure I can do it without breaking something :)
>
> Fixed in: http://anonscm.debian.org/gitweb/?p=bash-completion/bash-completion.git;a=commit;h=54bcdff3cf7e7e40f7ae0f4f20b53287653aa233
> Now even crazy things work:
>
> $ pwd
> /home
> $ umount ../dev//disk/../sd<TAB>
> ../dev//disk/../sda1 ../dev//disk/../sda4
> ../dev//disk/../sda3 ../dev//disk/../sdb1
> $ umount ../dev//disk/../sd
yeah, the first use-case now works;
$ umount pri<tab>
completes to "private". thanks !
Still, umount ../pri<tab> does not, but I believe it's not that a problem,
and probably not worse the hassle as these edge-cases could quickly
become as complex as trying to workaround COMP_WORDBREAKS.
regards
Raph
More information about the Bash-completion-devel
mailing list