unofficial mirror of emacs-devel@gnu.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: Sun, 15 Oct 2023 08:24:39 +0300	[thread overview]
Message-ID: <83edhwqwyx.fsf@gnu.org> (raw)
In-Reply-To: <878r85t1dk.fsf@tanaka.verona.se> (joakim@verona.se)

> X-Spam-Status: No, score=-0.999 tagged_above=-999 required=6.2
> 	tests=[ALL_TRUSTED=-1, DC_PNG_UNO_LARGO=0.001] autolearn=disabled
> From: joakim@verona.se
> Cc: emacs-devel@gnu.org
> Date: Sat, 14 Oct 2023 22:06:31 +0200
> 
> I managed to make a screenshot that shows the problem. In the image I
> made an emacs window with some black text on red background.
> 
> If I move the cursor just one line, you can see that 2 large regions
> become blurred. Since I just moved the cursor one line down, its rather
> confusing why these 2 seemingly unrelated regions should be redrawn.

It is not Emacs that's doing that.  When you move the cursor, Emacs
redraws just two characters: the one where the cursor was before the
move, and the one where it is after the move.  It can also redraw a
small part of the mode line: if the cursor is moved vertically, the
part with the line number will be redrawn, and if you have
column-number-mode enabled, the column number will be redrawn for any
cursor movement.  That's all.

I think Po Lu explained why you see what you see.  If disabling
double-buffering doesn't help, I think the root cause is the VNC
software you use, which must somehow decide which portions of the
screen to redraw.  Emacs is not the culprit here.



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

  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=83edhwqwyx.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 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).