| 1 |
On Thursday 25 July 2013 Douglas J Hunley wrote |
| 2 |
> On Wed, Jul 24, 2013 at 10:05 AM, Stefano Crocco |
| 3 |
<stefano.crocco@×××××.it>wrote: |
| 4 |
> > There are a few bugs regarding this issue, for example: 472938, 476992 and |
| 5 |
> > 477214. If I understand things correctly, all installed modules are |
| 6 |
> > enabled, |
| 7 |
> > but they're loaded "on-demand" (I guess this means the first time they're |
| 8 |
> > used, but I'm not sure). The way suggested in one of these bugs to have a |
| 9 |
> > working autocompletion is to source |
| 10 |
> > /usr/share/bash-completion/bash_completion |
| 11 |
> > from you .bashrc file. |
| 12 |
> > |
| 13 |
> > Stefano |
| 14 |
> |
| 15 |
> I agree w/ the user in 477214. This is completely broken. And the lack of |
| 16 |
> notice to the user post-emerge on how to set things up 'the new way' is |
| 17 |
> infuriating. Guess I'll add this to my 'check back in 6 months to see if |
| 18 |
> they've got it sorted' list |
| 19 |
> |
| 20 |
> Thanks Stefano |
| 21 |
> |
| 22 |
> -- |
| 23 |
> Douglas J Hunley (doug.hunley@×××××.com) |
| 24 |
> Twitter: @hunleyd Web: |
| 25 |
> douglasjhunley.com |
| 26 |
> G+: http://goo.gl/sajR3 |
| 27 |
|
| 28 |
I agree with you about the lack of a post-emerge message! I spent at least one |
| 29 |
hour the other day trying to understand why suddenly bash completion wasn't |
| 30 |
working anymore. I think all of this is still a work in progress, however, |
| 31 |
since the eselect package still installs the man page for the bashcomp module |
| 32 |
(bashcomp.eselect)! |
| 33 |
|
| 34 |
Stefano |
Archives