From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: luangruo@yahoo.com, 66247@debbugs.gnu.org
Subject: bug#66247: 29.1; Transient frame problems with Emacs 29 on MS Windows
Date: Tue, 10 Oct 2023 18:35:45 +0300 [thread overview]
Message-ID: <83edi2v6b2.fsf@gnu.org> (raw)
In-Reply-To: <SJ0PR10MB548809B50C897930974F0E73F3CDA@SJ0PR10MB5488.namprd10.prod.outlook.com> (message from Drew Adams on Tue, 10 Oct 2023 15:13:19 +0000)
> From: Drew Adams <drew.adams@oracle.com>
> CC: "luangruo@yahoo.com" <luangruo@yahoo.com>,
> "66247@debbugs.gnu.org"
> <66247@debbugs.gnu.org>
> Date: Tue, 10 Oct 2023 15:13:19 +0000
>
> 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.
This comes from Unix, where each frame can be on a different X
display, and therefore could use a different display driver.
next prev parent reply other threads:[~2023-10-10 15:35 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
2023-10-10 15:35 ` Eli Zaretskii [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83edi2v6b2.fsf@gnu.org \
--to=eliz@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.