Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Still there's a little zle_refresh bug
- X-seq: zsh-workers 865
- From: Wayne Davison <wayne@xxxxxxxxxxxxxxxxxx>
- To: Mark Borges <mdb@xxxxxxxxxxxx>
- Subject: Re: Still there's a little zle_refresh bug
- Date: Wed, 27 Mar 1996 15:06:54 -0800
- Cc: Zoltan Hidvegi <hzoli@xxxxxxxxxx>, Zsh hacking and development <zsh-workers@xxxxxxxxxxxxxxx>
- In-reply-to: mdb's message of 27 Mar 1996 13:16:16 -0700. <vkybom5m27.fsf@xxxxxxxxxxxxxxxxxx>
Mark Borges writes:
> I'm still seeing [a zle_refresh bug] on my solaris-2.3/2.5 platforms
It's a problem that depends on the insert-character terminal attribute
being present. Using your example of a series of '1234567890's on a
line with a '0' as the last character before the line-wrap, I get the
following output when I type the '*' prior to the '5' (using an xterm
that includes the insert-character attribute as "^[[@"):
*567890^M^[[@0
As you can see, it outputs enough characters to get down to the next
line (which includes outputting the NEW first character on the next
line) and then tries to do an insert at the start of the line. If
it had output the OLD first character when forcing a line wrap (or
had done the insert of the '1' at the second position) it would have
worked correctly.
In the case of a terminal without any insert character, it outputs the
following:
*567890^M01234567890
In this case it would still be OK for the force-a-line-wrap character
to be the OLD first character on the line since it gets overwritten.
I don't have time to fix the problem at the moment, but I hope that
this diagnosis will allow someone else to tweak the code.
..wayne..
Messages sorted by:
Reverse Date,
Date,
Thread,
Author