This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: bash: tab completion failure from (but not at) /
- From: Thorsten Kampe <thorsten at thorstenkampe dot de>
- To: cygwin at cygwin dot com
- Date: Tue, 11 May 2004 12:01:03 +0200
- Subject: Re: bash: tab completion failure from (but not at) /
- References: <E1BNQmW-0004rS-00@quimby.gnus.org>
* <fergus@bonhard.uklinux.net> (2004-05-11 08:25 +0100)
> Just lately (all recent snapshots including 20040510) I'm noticing a failure
> with tab completion for pathnames beginning /. Thus, I would expect, and in
> the past have achieved
>
> ls /ho<TAB>
> ls /home/
> or
> md5sum /us<TAB>loc<TAB>
> md5sum /usr/local/
>
> and so on.
>
> Now, all I am getting from ls /ho<TAB> or md5sum /us<TAB> is a system beep
> (i.e. "error!" or some kind of uncertainty or ambiguity affecting bash's
> interpretation).
>
> For pathnames starting elsewhere, there's not a problem. E.g. from HOME I
> can press
>
> cd st<TAB>
> cd stash
>
> or (cf. problem described above) if I actually *move* to / I can press
>
> ls ho<TAB>
> ls home/
> or
> md5sum us<TAB>loc<TAB>
> md5sum usr/local/
>
> I attach the output from cygcheck -srv. My ~/.inputrc has not altered for
> many months and includes the two lines
>
> set completion-ignore-case On
> set show-all-if-ambiguous On
I can confirm that almost identically (although I very rarely use
bash): under rxvt the cursor "jumps" in the next row and hangs there
for about a minute or more until the results are shown. The next
<TAB> then shows output immediately (as it should be).
The wrong behaviour doesn't show if i want to complete paths or files
not starting with "/" or if I am already in "/".
Thorsten,
using the latest bash and the latest Cygwin snapshot
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/