Re: backward-kill-word is not refreshing correctly

[Jay Freeman (saurik)]

On Mar 18, 6:55 pm, M...@ice.filescope.com, Zy...@ice.filescope.com
wrote:
...
>         When I type a long string of text and start pressing ctrl-W to 
> backwards-kill words, bash deletes the words but doesn't visually refresh 
> (the words still appear on the command line). This was not occurring for me 
> in the 3.x series of Bash.
>
> Repeat-By:
>         Write this text on the command line: "sample text sample text sample 
> text sample text sample text". Start pressing ctrl-W and notice it takes a 
> few kill-words before the words start disappearing.
>
> --Matt Zyzik

I having a problem similar to this. For me, kill-word /never/
refreshes the screen. Additionally, moving up/down through the command
history doesn't always cause a refresh either (in a manner
deterministic but stochastic).

I am using 4.0.17 on arm-apple-darwin9. I also cannot reproduce this
problem with bash 3.2. Unfortunately, I cannot reproduce this problem
on x86_64-unknown-linux-gnu.

I have tried building bash 4.x against ncurses 5.4 and 5.7, I have
tried compiling it against a standalone readline 6.x and using a built-
in copy, and I have tried compiling both for thumb and arm. I also
have tried copying the terminfo database off of my working x86_64 box
and I have even tried running without any terminfo database, in the
hope of determining why I can't reproduce the problem on my server.

Does anyone have any hints on what I could do to debug this? What
sections of code this might be using? I know very little about how
bash/readline/ncurses work together to handle this problem: even just
saying "check out these couple functions" could be useful, so I could
start seeing if they are getting called correctly.