Mark Knecht schreef: > Hi, On one machine of mine, and only one machine, bash completion is > not working for my user account when I try to complete a path. I hit > tab and nothing happens. Bash completion is working for files though. > I can do bash completion in my home directory and get a list of > files, but if I try to complete /usr/sr but hitting a tab it just > sits and does nothing. > > It works fine for root. > > What turns this feature on for a user? I copied a good .bashrc file > from a working machine over and logged back into the bad machine but > that didn't fix it. > > man bash makes it look like it should be on by default. > > Thanks for the unix lesson. > > Cheers, Mark
Yes, I have a similar problem, but bash-completion doesn't work correctly for anybody (user or su root). I uncommented the bash completion command in both ~/.bashrcs long ago, and at first the problem was only for root (which was weird enough); now (what constitutes 'now' as opposed to 'previously' I don't know) if I hit tab when filling in a path or a filename, as you said, nothing happens; if I fill in the rest of the path manually, the file is not found-- because my use of the TAB key has invisibly taken me up one directory (where the file does not exist). When I hit enter, I find that if I had started in /usr/local/src, I am now in /usr/local, for example. This occurs under various terminals (aterm, gnome-terminal, multi-gnome-terminal, xterm), although bash-completion fails differently under each of them (which is also weird). I know something has changed, but not what. Although.... now that I'm looking into this (which I had not really taken time to do, so I wasn't really 'worrying' about it as I had put this annoyance on my secondary 'to-do/fix' list, despite the fact that it's a major annoyance) I notice that I have both bash-completion and bash-completion-config installed-- and the man page for bash-completion-config says that the config files are in /etc/bashcomp-configrc, if it exists, or $HOME/.bashcomp-configrc, if it exists. So at least I probably need to check there first to see if bash-completion has in fact been set, since there is no mention of ~/.bashrc and perhaps those settings are now invalid, or in conflict. Something for you to check as well, Mark? Holly -- [email protected] mailing list
