On 10/24/05, Holly Bostick [EMAIL PROTECTED] wrote:
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
Holly,
Interesting, but somewhat different than mine. What I'm finding
this morning is that as a user it will complete some paths. For
instance here is completes for a path in my directory:
[EMAIL PROTECTED] ~ $ pwd
/home/mark
[EMAIL PROTECTED] ~ $ ls CODE/
xfst-0.4 xfst-0.4.tar.gz
[EMAIL PROTECTED] ~ $ cd CODE/xfst-0.4/
Makefile fst.oinstall-sh vst/ xfst
README fstconfig.c jackvst.hvsti.c xfst.exe.so
audiomaster.cfstinfofile.cjfst.c vsti.o
audiomaster.ofstinfofile.ojfst.o vstinfo.c
fst.cgtk.creadme.jack-fst vstwin.c
fst.hgtk.otags vstwin.o
[EMAIL PROTECTED] ~ $ cd CODE/xfst-0.4/vst
vst/ vsti.c vsti.o vstinfo.c vstwin.c vstwin.o
[EMAIL PROTECTED] ~ $ cd CODE/xfst-0.4/vst
[EMAIL PROTECTED] ~/CODE/xfst-0.4/vst $ pwd
/home/mark/CODE/xfst-0.4/vst
[EMAIL PROTECTED] ~/CODE/xfst-0.4/vst $
and for a file:
[EMAIL PROTECTED] ~ $ pwd
/home/mark
[EMAIL PROTECTED] ~ $ ls CODE/xfst-0.4/
Makefile fst.oinstall-sh vst/ xfst
README fstconfig.c jackvst.hvsti.c xfst.exe.so
audiomaster.cfstinfofile.cjfst.c vsti.o
audiomaster.ofstinfofile.ojfst.o vstinfo.c
fst.cgtk.creadme.jack-fst vstwin.c
fst.hgtk.otags vstwin.o
[EMAIL PROTECTED] ~ $ ls CODE/xfst-0.4/vst
vst/ vsti.c vsti.o vstinfo.c vstwin.c vstwin.o
[EMAIL PROTECTED] ~ $ ls CODE/xfst-0.4/vstinfo.c
CODE/xfst-0.4/vstinfo.c
[EMAIL PROTECTED] ~ $
It works for hidden direcotries and files:
[EMAIL PROTECTED] ~ $ cd .wine/
dosdevices/ drive_c/ system.reg user.reg userdef.reg
[EMAIL PROTECTED] ~ $ cd .wine/drive_c/
My Documents/ Program Files/ windows/
[EMAIL PROTECTED] ~ $ cd .wine/drive_c/windows/
Application Data/ fonts/regedit.exe system32/
winebrowser.exe
Start Menu/ inf/ rundll32.exe temp/
winhelp.exe
_isenv31.ini notepad.exe system/ uninstall.exe
winhlp32.exe
command/ profiles/ system.iniwin.ini
[EMAIL PROTECTED] ~ $ cd .wine/drive_c/windows/
However it will not complete for /usr, /bin or /var:
[EMAIL PROTECTED] ~ $ ls /us
[EMAIL PROTECTED] ~ $ ls /bi
[EMAIL PROTECTED] ~ $ ls /var
This seems almost like a permissions issue. However I can cd /usr/src,
I just cannot bash complete it:
[EMAIL PROTECTED] ~ $ cd /usr/src
[EMAIL PROTECTED]
