1 |
Mick wrote: |
2 |
> On Sunday 04 January 2009, Graham Murray wrote: |
3 |
>> Willie Wong <wwong@×××××××××.EDU> writes: |
4 |
>>> Before I file a bug, I want to see if this is reproducible by others: |
5 |
>>> |
6 |
>>> After I boot into the console, if I type anything and then hit <tab> |
7 |
>>> for the bash completion, it gives an error |
8 |
>>> -bash: _filedir: command not found |
9 |
>>> The weird thing is that if I start X and try the same in an aterm, the |
10 |
>>> tab completion works as expected. |
11 |
>>> |
12 |
>>> I am currently on bash-completion-20081218, does anyone else have the |
13 |
>>> same problem? |
14 |
>> I only saw the problem with vim, and then only for user root as a normal |
15 |
>> user it worked fine. So I disabled bash completion for vim. |
16 |
> |
17 |
> Check your relevant ~/.bashrc for this: |
18 |
> |
19 |
> ##uncomment the following to activate bash-completion: |
20 |
> #[ -f /etc/profile.d/bash-completion ] && \ |
21 |
> source /etc/profile.d/bash-completion |
22 |
|
23 |
There's not such entry in my .bashrc. |