Re: bug in bash completion?

[Mike Miller <mbmiller at taxa dot epi dot umn dot edu>]

On Tue, 20 Sep 2005, Scott Evans wrote:

> I just did a big Cygwin upgrade, which included a jump to bash 3.00.16(11)
> from 2.x.  Completion now seems a bit broken:
>
> [tmp] $ ls a.            (press TAB)
> a.el    a.html  a.txt
> [tmp] $ ls a..           (extra period shown but not really there)
>
>
> My PS1 is set thusly:
> PS1="\[\e]2;\H (\u) \w\a\][\W] $ "
>
> The bug goes away if I do
> PS1="$ "
>
> I don't see this on a Fedora system running bash 3.00.16(1).
>
> Known bug?  Problem on my system?  Is there other useful info I could
> offer?


FWIW, I see the same thing.  After the extra period appears, if I hit 
Ctrl-L to clear the screen, the extra period is still there, but if I hit 
Ctrl-A (beginning of line), then Ctrl-L, the extra period disappears.  If 
I move the cursor back and forth on the line while the extra period is 
there, hitting Ctrl-L now and then, various weird things happen with the 
characters moving about on the command line.

It isn't just periods at the end of lines - it's any character at the end 
of the uncompleted line.

Mike

--
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/