| 1 |
On Wed, 06 May 2015 12:44:16 +0300 |
| 2 |
Nikos Chantziaras <realnc@×××××.com> wrote: |
| 3 |
|
| 4 |
> If that is the case, then in order to completely transition to the |
| 5 |
> new system, you would have to re-emerge everything that installs |
| 6 |
> bashcomp files. Also, delete all your bashcomp eselect files. The new |
| 7 |
> system has everything enabled by default and eselect is used to |
| 8 |
> actually disable bashcomp for all packages and whitelist the only you |
| 9 |
> enable. This can cause problems if you have old and new files lying |
| 10 |
> around. |
| 11 |
|
| 12 |
Thanks for this. I'm not the OP, but broken bash completion has |
| 13 |
been bothering me for a while. Somehow I'd gotten the mistaken |
| 14 |
impression that it was supposed to heal itself over time as the |
| 15 |
programs that install bashcomp files were rebuilt with updates, without |
| 16 |
me having deal with any cruft. |
| 17 |
|
| 18 |
> I think there was a news item on how to transition from the old to |
| 19 |
> the new setup. No idea where to find it if you don't have it in |
| 20 |
> "eselect news list" anymore :-/ |
| 21 |
|
| 22 |
At the time, I was on the lookout for such a news item and I never saw |
| 23 |
one. Always possible that was my fault, but I really think there was |
| 24 |
no such item. |
| 25 |
|
| 26 |
Also, if I've correctly understood what you wrote above, |
| 27 |
<https://wiki.gentoo.org/wiki/Bash#Tab_completion> needs an overhaul. |
| 28 |
(Conversely, if it doesn't need an overhaul, my understanding is still |
| 29 |
faulty and I'll be back for some hand-holding!) |
Archives