From: Mark Borges <mdb@cdc.noaa.gov>
To: Zoltan Hidvegi <hzoli@cs.elte.hu>
Cc: zsh-workers@math.gatech.edu (Zsh hacking and development)
Subject: Re: Still there's a little zle_refresh bug
Date: 27 Mar 1996 13:16:16 -0700 [thread overview]
Message-ID: <vkybom5m27.fsf@suomi.cdc.noaa.gov> (raw)
In-Reply-To: Zoltan Hidvegi's message of Fri, 15 Mar 1996 16:02:05 +0100 (MET)
Geoff posted a second patch (in article #831) for zle_refresh. Was
that supposed to fix this particular bug (which was posted before the
2nd patch), or not?
If it was, I'm still seeing it on my solaris-2.3/2.5 platforms, and will
invetigate further if it is in fact platform-dependent.
Just curious.
-mb-
>> On Fri, 15 Mar 1996 16:02:05 +0100 (MET),
>> Zoltan Hidvegi(ZH) wrote:
ZH> The last patch from Geoff really fixes almost all zle_refresh problems
ZH> except one. This does not happen on all machines. It is reproducible on
ZH> Linux with ncurses and on Solaris with Linux console or xterm. Both use
ZH> terminfo. Type in a long line which appears wrapped on the screen. Then
ZH> insert a charater near the end of the first screen line, e.g. here -------|
ZH> V
ZH> hzoli ~ % 12345678901234567890123456789012345678901234567890123456789|1234567890
ZH> 1234567890
ZH> Here is what happens if you inserted a `*':
ZH> hzoli ~ % 12345678901234567890123456789012345678901234567890123456789|1234*56789
ZH> 00234567890
ZH> As you see the 0 is duplicated on the wrapped line and 1 disappears.
ZH> But this only happens if you insert something after the `|' character above.
ZH> Also there should be at least 10 characters in the second screen line.
next prev parent reply other threads:[~1996-03-27 21:50 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 [this message]
1996-03-27 23:06 ` Wayne Davison
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=vkybom5m27.fsf@suomi.cdc.noaa.gov \
--to=mdb@cdc.noaa.gov \
--cc=hzoli@cs.elte.hu \
--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).