Okay, like always, this is an I-D-ten-T error.
On Mon, Jan 05, 2009 at 02:20:19PM -0500, Penguin Lover Willie Wong squawked:
> So this suggests that, though I have not checked on my laptop, that on
> my aterms bash-completion is actually NOT activated, since my .bashrc
> almost certainly included the line to source bash-completion and not
> bash-completion.sh, which explains the different behaviour between an
> aterm and a login console.
This is confirmed. My .bashrc didn't have the right file for
bash-completion. Now it does and the behaviour on the console agrees
with that in the aterm.
> The next postulate is that since Graham noticed the behaviour only
> manifesting itself for vim and turning off the vim completion (I
> remember vaguely that on my laptop 'eselect bashcomp list --global'
> shows vim completion as enabled) that this maybe a bug with the module
> relating to bash completion for vim.
This is related to the other part of the ELOG which I didn't carefully
read. The _filedir problem was that the _filedir function is defined
in the "base" module for bash completion, which is a new addition in
the current version. By reading the configs for the previous setup,
the "base" module is not enabled by default. The "vim" module calls
_filedir, which is undefined, and hence the error.
The solution:
eselect bashcomp enable --global 2
(on my box 2 corresponds to the base module).
Best,
W
--
Proof that "Suki is good":
according to spaceballs: "[now we know evil will
always triumph, because] good is dumb"
according to S: "ok, now I feel really dumb"
the proof follows.
~~~~~~~
(on W's attempt to prove the phrase "suki is good" by syllogism)
S: it's okay, you don't need to proove [sic] it: it's a definition
W: nice
S: i spelled prove wrong
S: geez
W: don't worry
W: that doesn't make you evil.
Sortir en Pantoufles: up 760 days, 17:38
