From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: "66247@debbugs.gnu.org" <66247@debbugs.gnu.org>
Subject: bug#66247: 29.1; Transient frame problems with Emacs 29 on MS Windows
Date: Fri, 29 Sep 2023 10:49:26 +0800 [thread overview]
Message-ID: <87ttrdn16x.fsf@yahoo.com> (raw)
In-Reply-To: <SJ0PR10MB548855087FCCDF3EECEFB25BF3C0A@SJ0PR10MB5488.namprd10.prod.outlook.com> (Drew Adams's message of "Fri, 29 Sep 2023 02:22:00 +0000")
Drew Adams <drew.adams@oracle.com> writes:
> Thank you very much! That helps.
>
> I see mention of this in NEWS, now. And I see
> it described in (elisp) `Management Parameters'.
>
> However, the positive reason that the default
> behavior was changed is not really developed.
> Both NEWS and the Elisp manual just say that
> the default behavior (double buffering) aims
> "to reduce display flicker". Can you (and the
> doc) please say more?
No, because the flicker manifests differently for each person who
encounters it.
> And this language in the manual is, I think,
> unfortunate: if you "pine for that retro,
> flicker-y feeling" then set the parameter to t.
I agree.
> Has anyone ever really reported any such flicker
> on MS Windows? I've never noticed any "display
> flicker" there. Quite the opposite. I used
That's subject to the graphics driver installed, I believe. Many MS
Windows users reported severe flicker while scrolling in the past, a
problem that has all but vanished with the introduction of double
buffering.
next prev parent reply other threads:[~2023-09-29 2:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-28 1:36 bug#66247: 29.1; Transient frame problems with Emacs 29 on MS Windows Drew Adams
2023-09-29 1:21 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-29 2:22 ` Drew Adams
2023-09-29 2:49 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-09-29 16:17 ` Drew Adams
2023-09-29 16:32 ` Eli Zaretskii
2023-09-29 18:21 ` Drew Adams
2023-09-30 13:42 ` Eli Zaretskii
2023-09-30 15:22 ` Drew Adams
2023-09-30 15:36 ` Eli Zaretskii
2023-10-09 18:33 ` Drew Adams
2023-10-09 18:56 ` Eli Zaretskii
2023-10-09 19:49 ` Drew Adams
2023-10-10 12:00 ` Eli Zaretskii
2023-10-10 15:13 ` Drew Adams
2023-10-10 15:35 ` Eli Zaretskii
2023-10-10 15:53 ` Drew Adams
2023-10-10 18:46 ` Eli Zaretskii
2023-10-10 21:27 ` Drew Adams
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=87ttrdn16x.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=66247@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--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).