all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: joakim@verona.se
Cc: emacs-devel@gnu.org
Subject: Re: How to debug emacs repaint problems?
Date: Sat, 14 Oct 2023 22:15:10 +0300	[thread overview]
Message-ID: <83jzrpqam9.fsf@gnu.org> (raw)
In-Reply-To: <87fs2duld0.fsf@tanaka.verona.se> (joakim@verona.se)

> From: joakim@verona.se
> Date: Sat, 14 Oct 2023 20:09:31 +0200
> 
> Hello,
> 
> I have a long standing problem where it appears that my build of emacs
> seems to invalidate a lot of regions on screen, which leads to flicker
> in my setup of vnc. 
> 
> This flicker problem doesnt appear so much in the emacs that is
> installed by my distro, which is fedora, emacs 28.
> 
> It would be easier to debug this if emacs could be persuaded to give
> some visual hints of which regions its invalidating. Is this possible?

Not AFAIU, since Emacs doesn't invalidate any regions.  It decides by
itself which parts of the screen need to be redrawn, and then does
that.

> I use these settings in turbovnc:
> Tight+Low quality jpeg(WAN)
> /opt/TurboVNC/bin/tvncconfig -set ALR=1
> /opt/TurboVNC/bin/tvncconfig -set ALRAll=true
> 
> The idea is that a low quality codec should be used to refresh
> invalidated rects, and then after a while be losslessly refreshed.
> This works well in applications that dont invalidate the entire window,
> when only small parts of the window needs to be changed.

I don't know anything about turbovnc, but what you say is not how
Emacs display works.

Btw, does the flickering happen with text-mode frames or GUI frames?
And which part(s) of the Emacs display flicker?



  reply	other threads:[~2023-10-14 19:15 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 [this message]
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
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

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

  git send-email \
    --in-reply-to=83jzrpqam9.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=joakim@verona.se \
    /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.