1 |
Dnia 2013-09-09, o godz. 18:12:08 |
2 |
Nikos Chantziaras <realnc@×××××.com> napisał(a): |
3 |
|
4 |
> On 09/09/13 13:05, Michał Górny wrote: |
5 |
> > Dnia 2013-09-09, o godz. 12:50:03 |
6 |
> > Samuli Suominen <ssuominen@g.o> napisał(a): |
7 |
> > |
8 |
> >> On 09/09/13 12:24, Michał Górny wrote: |
9 |
> >>> 1. how to properly disable completions the 'new way'? |
10 |
> >> |
11 |
> >> something like |
12 |
> >> http://blog.onetechnical.com/2012/06/19/disable-bash-autocompletion-on-ubunt/ |
13 |
> >> should be replicated at wiki.gentoo.org |
14 |
> > |
15 |
> > Did you actually try that? |
16 |
> > |
17 |
> > Trying plain: |
18 |
> > |
19 |
> > complete -r git |
20 |
> > |
21 |
> > it removes git completion indeed. But when I type 'git <tab>', it is |
22 |
> > loaded back :). |
23 |
> |
24 |
> You can disable the "bash-completion" USE flag of dev-vcs/git. This |
25 |
> isn't a real solution, of course, since you need to recompile the whole |
26 |
> package every time you want to disable or enable bash completion. But |
27 |
> if you don't intend to actually ever use Git's completion, then this |
28 |
> should work. |
29 |
|
30 |
And it is a bug since completions are supposed to be installed indep of |
31 |
USE flags. |
32 |
|
33 |
But above all, I'm pointing out that we're pointing users towards |
34 |
a solution that simply does not work. |
35 |
|
36 |
-- |
37 |
Best regards, |
38 |
Michał Górny |