unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 59265@debbugs.gnu.org, "Francesco Potortì" <pot@gnu.org>
Subject: bug#59265: 27.1; emacs apparently redraws the entire X window for every update
Date: Tue, 15 Nov 2022 21:57:23 +0800	[thread overview]
Message-ID: <87leocfhh8.fsf@yahoo.com> (raw)
In-Reply-To: <83leocibu6.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 15 Nov 2022 15:30:57 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

> One thing I can suggest to try is disable double-buffering.  I have no
> idea what it can do with Xpra (since I don't really know how does Xpra
> do its job, whatever that is).

Yes, I explained what the problem is (and it isn't in Emacs) earlier:

Judging by the debug info provided in the Xpra bug report, it is relying
on the Damage extension to report window damage.  The Damage extension
always reports damage to the entire window upon a DBE buffer swap, which
is almost inconsequential when connected to an actual remote X server (I
do that every day), but not when a program like Xpra tries to ferry
pixmap contents over the wire.

Relying on Composite and Damage to send application contents over the
wire is fundamentally the wrong approach.  I suspect Xpra has to be
written as an X server driver (as its name applies), and that after
doing so, its DBE implementation has to be fixed to only call the
CopyArea GC op on areas of the back buffer that really changed.

So this isn't really a bug in Emacs, sorry.  You can work around the
problem by turning off double buffering, but that means you will also
need to put up with flicker.





  reply	other threads:[~2022-11-15 13:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-14 16:39 bug#59265: 27.1; emacs apparently redraws the entire X window for every update Francesco Potortì
2022-11-15  0:46 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-15 13:30 ` Eli Zaretskii
2022-11-15 13:57   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-11-15 14:04     ` Francesco Potortì
2022-11-24 18:37     ` Stefan Kangas

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=87leocfhh8.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=59265@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=pot@gnu.org \
    /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).