Running Debian unstable on my laptop, and testing on my home system,
bash completion on filenames has stuffed up some time recently. I see
no bugs in the BTS, has anyone else come across this?
I can complete on anything that has relevant functions defined in
/etc/bash_completion, but the lines between # START exclude, with the
complete -f -X entries, will hang the shell (with no beep) when I try
to tab complete. No more characters are accepted into bash until I
press ctrl-C.
If I 'set -vx' the shell, I get the following, when pressing TAB in a
directory that has an uptime.png file in it:
$ xv upt<TAB>+ local IFS cur xspec
+ IFS=
+ COMPREPLY=()
+ cur=fac
+ _expand
+ '[' fac '!=' fac ']'
+ [[ fac == \~*/* ]]
+ [[ fac == \~* ]]
++ sed -ne '/ xv/{p;q;}'
sed's stdin seems almost to be attched to the terminal, at least
/proc/$sed-pid/fd/0 is a /dev/pts device...
I try typing in somehting, or pressing ctrl-d to simulate
end-of-stream, and nothing happens.
I tried reinstalling bash and everything that provided
/etc/bsah_completion.d, I tried downgrading it all to stable, etc, but
nothing has worked. I don't know what I changed or installed that
might have broken this. Any ideas?
Any more information, or things in my environment I should provide? I
am thinking this is not a bug, just a problem with my setup - probably
got plenty of 2 year old cruft sitting around the system messing
things up...
--
TimC -- http://astronomy.swin.edu.au/staff/tconnors/
Beware of Programmers who carry screwdrivers.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
