unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Drew Adams <drew.adams@oracle.com>, 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: Mon, 9 Oct 2023 18:33:48 +0000	[thread overview]
Message-ID: <SJ0PR10MB5488486760446C211C899BC4F3CEA@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <SJ0PR10MB54885BB239D3F8048E618D1BF3C7A@SJ0PR10MB5488.namprd10.prod.outlook.com>

In addition to the problems described, even when
parameter `inhibit-double-buffering' is `t':

When applying a set of frame position and size
modifications, the transient appearance shows
not only the scroll bar in the initial position
but the overall frame, even after it's resized,
remains in the original position.  The final
position and location of the scroll bar are not
realized at the same time as the frame is resized.

There is a _general_ regression wrt the behavior
in all previous Emacs releases (back through 20,
at least).  Setting `inhibit-double-buffering' to
`t' removes only some of the problems introduced.

You may say that the rest of the frame-display
implementation, besides the addition of double
buffering, wasn't changed for Emacs 29, but that
doesn't seem to be the case.  Something has led
to a regression wrt frame display - multiple
frame parameters.

When a set of parameters are changed with one
`modify-frame-parameters' the effect is not to
change them all at once - and that's new (a
regression).  The frame is resized, and some
time later the other frame modifications take
effect.





  parent reply	other threads:[~2023-10-09 18:33 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 [this message]
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=SJ0PR10MB5488486760446C211C899BC4F3CEA@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).