From: Eli Zaretskii <eliz@gnu.org>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: lbsmtp@gmail.com, 1867@debbugs.gnu.org
Subject: bug#1867: Resizing window causes text flickering when using antialiased font on X
Date: Thu, 06 Oct 2011 01:33:36 -0400 [thread overview]
Message-ID: <E1RBgaO-0003Bj-Qq@fencepost.gnu.org> (raw)
In-Reply-To: <8739f73xva.fsf@stupidchicken.com> (message from Chong Yidong on Wed, 05 Oct 2011 17:57:29 -0400)
> From: Chong Yidong <cyd@stupidchicken.com>
> Cc: "Jan D." <jan.h.d@swipnet.se>, 1867@debbugs.gnu.org, lbsmtp@gmail.com
> Date: Wed, 05 Oct 2011 17:57:29 -0400
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > The way redisplay is written, _any_ change to dimensions of _any_
> > window sets a flag that will cause a thorough redisplay of all the
> > windows on all the visible frames. However, I'd expect that redisplay
> > of any window not affected by the resizing be limited to redrawing the
> > cursor.
>
> Resizing a window redraws all windows on the same frame, even those
> unaffected by the resizing.
What do you mean by "redraws"? It generates the full desired glyph
matrices for each window, but there's code in dispnew.c that compares
the desired matrix with the current matrix, and only redraws the parts
that changed. Are you saying that this optimization is disabled? Do
you actually see the xterm backend redrawing each and every window in
this use case?
next prev parent reply other threads:[~2011-10-06 5:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-12 10:10 bug#1867: Resizing window causes text flickering when using antialiased font on X Bo Lin
2011-10-05 1:13 ` Glenn Morris
2011-10-05 7:01 ` Jan D.
2011-10-05 10:41 ` Eli Zaretskii
2011-10-05 17:34 ` Jan Djärv
2011-10-05 20:29 ` Eli Zaretskii
2011-10-05 21:16 ` Jan Djärv
2011-10-06 14:17 ` Jason Rumney
2011-10-05 21:57 ` Chong Yidong
2011-10-06 5:33 ` Eli Zaretskii [this message]
2011-10-06 6:05 ` Jan D.
2011-10-06 15:06 ` Chong Yidong
2011-10-06 19:38 ` Bo Lin
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=E1RBgaO-0003Bj-Qq@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=1867@debbugs.gnu.org \
--cc=cyd@stupidchicken.com \
--cc=lbsmtp@gmail.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.