Re: using meta-# with large strings results in misbehavior

[Chet Ramey]

Andreas Schwab wrote:
> Chet Ramey <chet.ramey@case.edu> writes:
> 
>> Mike Frysinger wrote:
>>
>>> doing something simple like (pasting 50 m chars and then 4 k chars):
>>> meta-50 m
>>> meta-4 k
>>> results in the string being drawn incorrectly.  it shows:
>>> mmmmmmmmmmmkkkkmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmm
>>> if i force a refresh with CTRL+L i see the right string:
>>> mmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmkkkk
>>>
>>> my $PS1 is set to:
>>> \[\e[0;33m\]\u\[\e[30;1m\]@\[\e[31;1m\]\h\[\e[30;1m\] \j:$? \[\e[34;1m\]\W 
>>> \$\[\e[0m\]
>>> which typically expands to:
>>> vapier@vapier 0:0 ~ $ 
>> I can't reproduce this running Terminal or xterm on MacOS X.  MacOS X
>> aterm gives some weird redisplays, but only when the second numeric
>> argument is > 10, and the final display is (usually) right.  I don't
>> see your results.
> 
> Set PS1='\[\e[1m\]xxxxxxxxxx\$\[\e[m\] ' and retry.

Nope, still don't see Mike's results.  I did find and fix one redisplay
bug that this causes, and that fix will be in the next release.

Chet

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer

Chet Ramey, ITS, CWRU    chet@case.edu    http://cnswww.cns.cwru.edu/~chet/