From: Nikos Chantziaras <realnc@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: bash-completion change?
Date: Sat, 27 Jul 2013 00:39:13 +0300 [thread overview]
Message-ID: <ksuqa2$cv7$1@ger.gmane.org> (raw)
In-Reply-To: <87txjhw2vh.fsf@nyu.edu>
On 26/07/13 22:13, gottlieb@nyu.edu wrote:
> On Fri, Jul 26 2013, Nikos Chantziaras wrote:
>
>> On 24/07/13 15:06, 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?
>>
>> As others pointed out, you now need to:
>>
>> source /usr/share/bash-completion/bash_completion
>>
>> in your ~/.bashrc. However, you also need to clean out anything in
>> /etc/bash_completion.d/ and then:
>>
>> ln -s /usr/share/bash-completion/gentoo /etc/bash_completion.d/
>>
>> Otherwise, completion for Gentoo stuff (like "emerge") will not be
>> available.
>
> Although I have a number of files and one subdirectory in
> /usr/share/bash-completion, I have neither
> /usr/share/bash-completion/bash_completion
> /usr/share/bash-completion/gentoo
>
> Presumably I have forgotten to turn something on; would you know what?
You probably forgot to re-emerge all packages that provide bash
completion files:
emerge -av1 \$(qfile -q -S -C /usr/share/bash-completion)
This is actually printed by app-shells/bash-completion when emerging it.
If you don't do that, all the completion files are in the wrong
directory. And yes, it will probably re-emerge *a lot* of packages, so
you might want to do that while you're AFK.
next prev parent reply other threads:[~2013-07-26 21:39 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
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 [this message]
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='ksuqa2$cv7$1@ger.gmane.org' \
--to=realnc@gmail.com \
--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