zsh-workers
 help / color / mirror / code / Atom feed
From: Wayne Davison <wayne@tenor.clarinet.com>
To: Mark Borges <mdb@cdc.noaa.gov>
Cc: Zoltan Hidvegi <hzoli@cs.elte.hu>,
	Zsh hacking and development <zsh-workers@math.gatech.edu>
Subject: Re: Still there's a little zle_refresh bug
Date: Wed, 27 Mar 1996 15:06:54 -0800	[thread overview]
Message-ID: <199603272306.PAA00382@tenor.clari.net> (raw)
In-Reply-To: mdb's message of 27 Mar 1996 13:16:16 -0700. <vkybom5m27.fsf@suomi.cdc.noaa.gov>

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



  reply	other threads:[~1996-03-27 23:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-03-15 15:02 Zoltan Hidvegi
1996-03-27 20:16 ` Mark Borges
1996-03-27 23:06   ` Wayne Davison [this message]
1996-03-28  8:43   ` mason
1996-03-28  9:34     ` mason

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=199603272306.PAA00382@tenor.clari.net \
    --to=wayne@tenor.clarinet.com \
    --cc=hzoli@cs.elte.hu \
    --cc=mdb@cdc.noaa.gov \
    --cc=zsh-workers@math.gatech.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).