On Sun, Jan 4, 2009 at 3:23 PM, Nikos Chantziaras <[email protected]> wrote: > Mick wrote: >> >> On Sunday 04 January 2009, Graham Murray wrote: >>> >>> Willie Wong <[email protected]> writes: >>>> >>>> Before I file a bug, I want to see if this is reproducible by others: >>>> >>>> After I boot into the console, if I type anything and then hit <tab> >>>> for the bash completion, it gives an error >>>> -bash: _filedir: command not found >>>> The weird thing is that if I start X and try the same in an aterm, the >>>> tab completion works as expected. >>>> >>>> I am currently on bash-completion-20081218, does anyone else have the >>>> same problem? >>> >>> I only saw the problem with vim, and then only for user root as a normal >>> user it worked fine. So I disabled bash completion for vim. >> >> Check your relevant ~/.bashrc for this: >> >> ##uncomment the following to activate bash-completion: >> #[ -f /etc/profile.d/bash-completion ] && \ source >> /etc/profile.d/bash-completion > > There's not such entry in my .bashrc.
Since the problem does not appear under X, bash is not broken and you probably have a mis-configuration somehow. The rc scripts that are run are sensitive to the nature of the session. Your console login is a "interactive login shell", while under X it's merely a "interactive shell". You might want to track down the scripts that run in the two situations. My first guess would be that your ~/.bashrc sets up completion, but that file is not called from /etc/profile. If that's not it you have some debugging to do. When I have to do something like that, I pepper all of the rc scripts with lines like [ -e /etc/conf.d/DEBUG ] && echo "~$USER/.bashrc: \$-='$-'"\ (modify according to what info you want and what script it's in) then touch or rm the file /etc/conf.d/DEBUG. Don't forget to include system scripts like /etc/profile and anything else mentioned in the man page (INVOCATION section). HTH -- Kevin O'Gorman, PhD
