From: Robert Pluim <rpluim@gmail.com>
To: Po Lu <luangruo@yahoo.com>
Cc: Eli Zaretskii <eliz@gnu.org>, Ken Brown <kbrown@cornell.edu>,
emacs-devel@gnu.org
Subject: Re: MS Windows double buffering
Date: Tue, 03 May 2022 10:23:24 +0200 [thread overview]
Message-ID: <87y1zj81oj.fsf@gmail.com> (raw)
In-Reply-To: <87v8urt3mk.fsf@yahoo.com> (Po Lu's message of "Sat, 30 Apr 2022 15:46:43 +0800")
>>>>> On Sat, 30 Apr 2022 15:46:43 +0800, Po Lu <luangruo@yahoo.com> said:
>> Here and elsewhere in the modified code, I'd like to have all the
>> changes that affect the no-double-buffering code to be conditioned on
>> some variable exposed to Lisp. That way, if and when someone reports
>> a problem that could be related to this feature, we could easily get
>> back to exactly the old code as it was before the changeset, and see
>> if the problem is indeed due to this change. For example, entering
>> the critical section above is one such change.
Po> Thanks. That's not something we do on X, but I will add such a
Po> variable.
For double-buffering itʼs a frame parameter called
`inhibit-double-buffering', so you could just reuse that.
Robert
--
next prev parent reply other threads:[~2022-05-03 8:23 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <877d791thh.fsf.ref@yahoo.com>
2022-04-28 8:51 ` MS Windows double buffering Po Lu
2022-04-28 9:42 ` Eli Zaretskii
2022-04-28 12:45 ` Po Lu
2022-04-29 3:36 ` Po Lu
2022-04-30 5:41 ` Po Lu
2022-04-30 6:50 ` Eli Zaretskii
2022-04-30 7:46 ` Po Lu
2022-04-30 9:10 ` Eli Zaretskii
2022-04-30 9:55 ` Po Lu
2022-04-30 10:23 ` Eli Zaretskii
2022-04-30 10:33 ` Po Lu
2022-04-30 10:55 ` Eli Zaretskii
2022-04-30 11:01 ` Po Lu
2022-04-30 11:32 ` Eli Zaretskii
2022-04-30 11:54 ` Po Lu
2022-05-03 8:23 ` Robert Pluim [this message]
2022-05-03 8:43 ` Po Lu
2022-04-30 17:34 ` Ken Brown
2022-04-30 18:25 ` Eli Zaretskii
2022-05-01 0:35 ` Po Lu
2022-05-01 16:00 ` Arash Esbati
2022-05-01 16:07 ` Eli Zaretskii
2022-05-01 16:11 ` Arash Esbati
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=87y1zj81oj.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=kbrown@cornell.edu \
--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).