From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: joakim@verona.se, emacs-devel@gnu.org
Subject: Re: How to debug emacs repaint problems?
Date: Sun, 15 Oct 2023 08:49:12 +0300 [thread overview]
Message-ID: <838r84qvtz.fsf@gnu.org> (raw)
In-Reply-To: <87zg0k8zqv.fsf@yahoo.com> (message from Po Lu on Sun, 15 Oct 2023 09:02:00 +0800)
> From: Po Lu <luangruo@yahoo.com>
> Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
> Date: Sun, 15 Oct 2023 09:02:00 +0800
>
> joakim@verona.se writes:
>
> > If so, it appears to me that my build of emacs redraws a lot of regions
> > unecessarily. So the my question is if its possible to make Emacs show
> > some hints of which areas its redrawing. Then I would know if the
> > problem is in emacs, or elsewhere.
> >
> > The emacs 28 in my distro doesnt flicker, nor does apps such as gedit.
>
> This is consequent upon double buffering. Being incapable of recording
> individual damage to window back buffers, the X server uniformly damages
> the whole front buffer whenever buffers are swapped.
>
> Should flicker be preferable to slow redisplay, disabling double
> buffering is the correct solution. But if not, use an X connection in
> place of VNC, enabling the transfer of only drawing commands.
Since double-buffering was introduced in Emacs 26, it still cannot
fully explain why Emacs 28 doesn't show this behavior.
However, as I explained in my other message, what Joakim sees is
definitely not the result of Emacs redisplay redrawing too large
portions of the screen, because Emacs doesn't do that. Some other
factor or software is at work here.
next prev parent reply other threads:[~2023-10-15 5:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-14 18:09 How to debug emacs repaint problems? joakim
2023-10-14 19:15 ` Eli Zaretskii
2023-10-14 19:47 ` joakim
2023-10-14 20:06 ` joakim
2023-10-14 21:29 ` joakim
2023-10-15 5:24 ` Eli Zaretskii
2023-10-15 1:02 ` Po Lu
2023-10-15 5:49 ` Eli Zaretskii [this message]
2023-10-15 11:02 ` joakim
2023-10-15 11:49 ` Po Lu
2023-10-15 12:17 ` joakim
2023-10-15 12:43 ` Po Lu
2023-10-15 13:31 ` joakim
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=838r84qvtz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=joakim@verona.se \
--cc=luangruo@yahoo.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).