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 re
burning shadow wrote:
Like I said, it's unlikely that this is the thing that makes the
difference, but you could
always have a quick try with the latest snapshot just in case:
http://cygwin.com/snapshots. It might also be trying the different
cygwin terminals, xterm
and rxvt as well as plai
Like I said, it's unlikely that this is the thing that makes the difference,
but you could
always have a quick try with the latest snapshot just in case:
http://cygwin.com/snapshots. It might also be trying the different cygwin
terminals, xterm
and rxvt as well as plain old dos console.
Oh,
On 30 May 2006 18:08, burning shadow wrote:
>> Since version 3, bash has had problems with readline causing spurious
>> 'ghost'
>> characters to echo to the screen, particularly when scrolling through the
>> history
>> buffer or using a prompt with non-printing chars in it. It may affect
>> c
Since version 3, bash has had problems with readline causing spurious 'ghost'
characters to echo to the screen, particularly when scrolling through the
history
buffer or using a prompt with non-printing chars in it. It may affect
completion too.
Is there any solution?
The real question
On 30 May 2006 17:40, burning shadow wrote:
> Since version 3 bash has problems with path completion.
Since version 3, bash has had problems with readline causing spurious 'ghost'
characters to echo to the screen, particularly when scrolling through the
history buffer or using a prompt with
6 matches
Mail list logo
