From: Ken Brown <kbrown@cornell.edu>
To: Eli Zaretskii <eliz@gnu.org>, Po Lu <luangruo@yahoo.com>
Cc: emacs-devel@gnu.org
Subject: Re: MS Windows double buffering
Date: Sat, 30 Apr 2022 13:34:32 -0400 [thread overview]
Message-ID: <fd3df792-a696-3299-15ce-f682d408fd73@cornell.edu> (raw)
In-Reply-To: <835ymr9i9v.fsf@gnu.org>
On 4/30/2022 2:50 AM, Eli Zaretskii wrote:
> . w32term.c is also used in the Cygwin w32 build, (which produces a
> Cygwin Emacs that uses the native MS-Windows GUI functions instead
> of X). Will this code work in that build? If not, the new code
> should be ifdef'ed away on Cygwin. Ken, can you please chime in
> and help us DTRT here?
I just built the Cygwin w32 build from git commit 0ea0aa255 and evaluated
(while t (redraw-display) (redisplay))
I saw some flicker in the menu bar but nowhere else. I tried the same thing in
a Cygwin w32 build of emacs-28.1, and there was severe flickering throughout the
frame. So there's a noticeable improvement.
I'll keep testing over the next few days and let you know if I see any problems.
Ken
next prev parent reply other threads:[~2022-04-30 17:34 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
2022-05-03 8:43 ` Po Lu
2022-04-30 17:34 ` Ken Brown [this message]
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=fd3df792-a696-3299-15ce-f682d408fd73@cornell.edu \
--to=kbrown@cornell.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--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).