bash 3.x path completion problems

[burning shadow]

I figured out it happens only with colored command prompt. Probably, I
have some errors in ansi codes, I tried different variants, here are
some of them:

PS1='\[\033]0;\w\007\033[32m\]\u\[\033[0m\]:\[\033[33m\]\w\[\033[0m\]\$ '
PS1='\[\033[32m\]\u\[\033[0m\]:\[\033[33m\]\w\[\033[0m\]\$ '

If I remove all ansi codes from PS1, everything looks as expected.

Please, point me, what do I do wrong.. I liked my colored string so much.. :)

Dave Korn wrote:

>> The problem is that 'qqq/qq/' thing. This was never happened to bash 2.05b.
>
>   The real question is whether the trailing 'qq/' is actually there in the input buffer or if it's just an optical illusion caused by the readline bug.  What happens if you immediately press enter?
>
>   BTW with all the latest updates (including cygwin dll from cvs, but that's probably not relevant) I can't reproduce your example:
>
> dk@rainbow /tmp/try_it> ls -la
> total 0
> drwxr-xr-x+ 4 dk Domain Users 0 May 30 17:42 .
> drwxrwxrwt+ 4 dk Users        0 May 30 17:42 ..
> drwxr-xr-x+ 2 dk Domain Users 0 May 30 17:42 games
> drwxr-xr-x+ 5 dk Domain Users 0 May 30 17:49 qqq
> -rwx------  1 dk Domain Users 0 May 30 17:42 s
> dk@rainbow /tmp/try_it> ls -la qqq/
> total 0
> drwxr-xr-x+ 5 dk Domain Users 0 May 30 17:49 .
> drwxr-xr-x+ 4 dk Domain Users 0 May 30 17:42 ..
> drwxr-xr-x+ 2 dk Domain Users 0 May 30 17:49 162567asd
> -rw-r--r--  1 dk Domain Users 0 May 30 17:43 qqq.txtx
> drwxr-xr-x+ 2 dk Domain Users 0 May 30 17:49 qwter
> drwxr-xr-x+ 2 dk Domain Users 0 May 30 17:49 wqyteuqt
> dk@rainbow /tmp/try_it> cd qqq/
> 162567asd/ qqq.txtx   qwter/     wqyteuqt/
> dk@rainbow /tmp/try_it> cd qqq/

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