From: Stefano Crocco <stefano.crocco@alice.it>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] bash-completion change?
Date: Wed, 24 Jul 2013 16:05:49 +0200 [thread overview]
Message-ID: <2563237.3cJmiOkv2O@casa> (raw)
In-Reply-To: <CALxYTP67-HpBSaajbhYsghY3XH=-_h9erTfxuWnJoNbYy9X70A@mail.gmail.com>
On Wednesday 24 July 2013 Douglas J Hunley wrote
> As of bash-completion-2.1-r1 it appears the eselect module is gone and the
> use of /etc/bash-completion.d is dead. Does this mean that all completions
> are enabled globally by default now? It used to be that you could turn each
> individual one on/off either globally or per user. Anyone know what the new
> 'one true way' is here?
>
> --
> Douglas J Hunley (doug.hunley@gmail.com)
> Twitter: @hunleyd Web:
> douglasjhunley.com
> G+: http://goo.gl/sajR3
There are a few bugs regarding this issue, for example: 472938, 476992 and
477214. If I understand things correctly, all installed modules are enabled,
but they're loaded "on-demand" (I guess this means the first time they're
used, but I'm not sure). The way suggested in one of these bugs to have a
working autocompletion is to source /usr/share/bash-completion/bash_completion
from you .bashrc file.
Stefano
next prev parent reply other threads:[~2013-07-24 14:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 12:06 [gentoo-user] bash-completion change? Douglas J Hunley
2013-07-24 14:05 ` Stefano Crocco [this message]
2013-07-25 12:14 ` Douglas J Hunley
2013-07-25 15:16 ` Stefano Crocco
2013-07-26 17:12 ` [gentoo-user] " Nikos Chantziaras
2013-07-26 19:13 ` gottlieb
2013-07-26 21:39 ` Nikos Chantziaras
2013-07-26 21:46 ` Bruce Hill
2013-07-26 23:23 ` Neil Bothwick
2013-07-27 14:49 ` gottlieb
2013-07-28 16:08 ` Neil Bothwick
2013-07-28 16:47 ` Nikos Chantziaras
2013-07-28 16:53 ` Alan McKinnon
2013-07-28 18:25 ` Neil Bothwick
2013-07-29 1:09 ` Nikos Chantziaras
2013-07-26 23:37 ` gottlieb
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2563237.3cJmiOkv2O@casa \
--to=stefano.crocco@alice.it \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox