public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Thomas Dickey <dickey@his.com>
To: cygwin-xfree@cygwin.com
Subject: Re: Strange xterm scrolling problem introduced in XTerm(289)
Date: Tue, 12 Feb 2013 23:51:00 -0000 [thread overview]
Message-ID: <20130212235048.GA13070@aerie.jexium-island.net> (raw)
In-Reply-To: <CAK-n8j4L1g2_pzUJuCn249d-9EmVbaL7nmMe11YOncV_5xokfQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1072 bytes --]
On Tue, Feb 12, 2013 at 04:22:05PM -0700, Jim Reisert AD1C wrote:
> On Tue, Feb 12, 2013 at 4:01 PM, Thomas Dickey wrote:
>
> > Did you run #288 before this update? (288 had several fixes for
> > Coverity warnings, one of the #289 changes fixed something that
> > I broke in addressing those).
>
> I believe I had been running #288 at one point. I just updated Cygwin
> and could only revert to 287 (not 288). There is no scrollback
> problem with this version.
hmm - _looking_ for the problem, I ran uxterm with valgrind (which reported
no problem...), but I resized the window back and forth a few times and
after several tries, got some debris on the screen which corresponds
to what you're describing. (Scrolling with the shifted pageup/pagedown
or with the scrollbar didn't produce it; it's the repainting due to
resizes dragging text out of the scrollback which gives the result).
thanks for the report (I'll work on this now)
--
Thomas E. Dickey <dickey@invisible-island.net>
http://invisible-island.net
ftp://invisible-island.net
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2013-02-12 23:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 21:54 Jim Reisert AD1C
2013-02-12 23:01 ` Thomas Dickey
2013-02-12 23:22 ` Jim Reisert AD1C
2013-02-12 23:51 ` Thomas Dickey [this message]
2013-02-13 0:41 ` Thomas Dickey
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=20130212235048.GA13070@aerie.jexium-island.net \
--to=dickey@his.com \
--cc=cygwin-xfree@cygwin.com \
/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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).