unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "luangruo@yahoo.com" <luangruo@yahoo.com>,
	"66247@debbugs.gnu.org" <66247@debbugs.gnu.org>
Subject: bug#66247: 29.1; Transient frame problems with Emacs 29 on MS Windows
Date: Tue, 10 Oct 2023 15:13:19 +0000	[thread overview]
Message-ID: <SJ0PR10MB548809B50C897930974F0E73F3CDA@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <83r0m2vga2.fsf@gnu.org>

> I see the same in Emacs 28, so this isn't a regression in Emacs 29.
> When Emacs needs to redraw the frame, it actually asks the MS-Windows
> GUI subsystem to do that, and the update takes time (and happens in a
> separate UI thread).  So these small lags are expected.

You're right about that.  So that simple recipe
isn't good enough.

I'm guessing that you're also right about the
only problem being the double-buffering.  I'm
guessing that for some reason things are just
somewhat slower in Emacs 29 for frame display,
so I notice the lingering scroll-bar position
more.

I think you can close this bug, the general
solution being to add (inhibit-double-buffering . t)
to `default-frame-alist'.
___

BTW, what's the rationale behind making this
a frame parameter rather than just an option
that affects all frames?  Presumably there is
some use case for having it ON or OFF for only
specific frames or groups of frames.  I'm
curious what such a use case might be.

Because of this choice, I need to customize
both `default-frame-alist' and
`special-display-frame-alist'.  (I know that
Emacs considers that option to be obsolete,
but it's very important to me.)  There are
other frame-display alists, as well, and
users might have still other alists governing
different groups/types of frames.

Again, I imagine there's a use case for this
frame parameter to be a frame parameter, as
opposed to just an option that affects all
frames, but so far, I can't imagine what such
a use case might be.





  reply	other threads:[~2023-10-10 15:13 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
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 [this message]
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=SJ0PR10MB548809B50C897930974F0E73F3CDA@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=66247@debbugs.gnu.org \
    --cc=eliz@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).