From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: larsi@gnus.org, 9366@debbugs.gnu.org
Subject: bug#9366: Display geometry change hook
Date: Tue, 22 Sep 2020 17:16:58 +0300 [thread overview]
Message-ID: <83v9g5x5et.fsf@gnu.org> (raw)
In-Reply-To: <8515b084-fd76-20e5-7452-83cb85adce2e@gmx.at> (message from martin rudalics on Tue, 22 Sep 2020 09:16:58 +0200)
> Cc: larsi@gnus.org, david@harpegolden.net, 9366@debbugs.gnu.org
> From: martin rudalics <rudalics@gmx.at>
> Date: Tue, 22 Sep 2020 09:16:58 +0200
>
> > Yes, I know about WM_DISPLAYCHANGE (although we currently only handle
> > the full-screen frames there).
>
> Has anyone ever confirmed that it correctly handles the full-screen
> frames?
I don't know. I don't have a system to try that.
> > But the corresponding X feature
> > requires the use of a special X module, and I don't know what happens
> > on macOS. So I thought a platform-independent method that always
> > works, and can be implemented in just one place, is a better
> > alternative.
>
> But such a platform-independent method on X would boil down to using the
> same special X module as the platform-dependent method. That is, we
> would try running XRANDR in either case ...
Do we use XRANDR to query the display geometry?
> > Besides, adding one more special event comes with minor disadvantages
> > of its own -- one more event to disregard in situations like
> > while-no-input etc.
>
> But at least on Windows we have to pay attention to such events anyway.
I didn't mean MS-Windows events (a.k.a. "messages"), I meant events in
the Emacs event queue. A message coming from the window manager
doesn't have to be converted to an Emacs event, it can be handled
directly.
next prev parent reply other threads:[~2020-09-22 14:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-25 5:16 bug#9366: Display geometry change hook David De La Harpe Golden
2011-08-25 5:55 ` Eli Zaretskii
2011-08-25 12:42 ` David De La Harpe Golden
2011-08-31 17:43 ` bug#9366: Attempting to add myself to this bug's CC list Edward O'Connor
2020-09-19 15:28 ` bug#9366: Display geometry change hook Lars Ingebrigtsen
2020-09-19 15:42 ` Eli Zaretskii
2020-09-20 8:14 ` martin rudalics
2020-09-20 8:25 ` Lars Ingebrigtsen
2020-09-20 8:56 ` Eli Zaretskii
2020-09-20 12:24 ` martin rudalics
2020-09-20 12:59 ` Eli Zaretskii
2020-09-21 7:26 ` martin rudalics
2020-09-21 14:21 ` Eli Zaretskii
2020-09-22 7:16 ` martin rudalics
2020-09-22 14:16 ` Eli Zaretskii [this message]
2020-09-23 7:15 ` martin rudalics
2020-09-23 7:47 ` Corwin Brust
2020-09-23 8:14 ` martin rudalics
2020-09-23 14:35 ` Eli Zaretskii
2020-09-23 14:29 ` Eli Zaretskii
2020-09-23 17:41 ` martin rudalics
2020-09-23 18:03 ` Eli Zaretskii
2020-09-22 15:04 ` Lars Ingebrigtsen
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=83v9g5x5et.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=9366@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=rudalics@gmx.at \
/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).