From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: salvino@coderedcorp.com, 51404@debbugs.gnu.org, 47291@debbugs.gnu.org
Subject: bug#51404: Support system dark mode on Windows 10
Date: Fri, 12 Nov 2021 08:19:22 +0200 [thread overview]
Message-ID: <83k0hdzyj9.fsf@gnu.org> (raw)
In-Reply-To: <87czn63wot.fsf@gnus.org> (message from Lars Ingebrigtsen on Fri, 12 Nov 2021 04:00:18 +0100)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: salvino@coderedcorp.com, 51404@debbugs.gnu.org, 47291@debbugs.gnu.org
> Date: Fri, 12 Nov 2021 04:00:18 +0100
>
> > Maybe. But some expert (which is not me) will have to explain what to
> > do when we receive these messages, or submit patches for that.
>
> On the Linux side, we convert the messages to input events and then
> react to that event from special-event-map, which seems like a
> reasonable structure.
I mean how to tell what the message wants us to do, i.e. which parts
of the UI to change and in what way.
next prev parent reply other threads:[~2021-11-12 6:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 4:46 bug#51404: Support system dark mode on Windows 10 Vince Salvino
2021-10-26 14:01 ` Eli Zaretskii
2021-10-26 16:18 ` Eli Zaretskii
2021-10-26 16:49 ` Vince Salvino
2021-10-26 17:05 ` Eli Zaretskii
2021-10-26 18:20 ` Vince Salvino
2021-10-27 21:41 ` Vince Salvino
2021-10-28 7:15 ` Eli Zaretskii
2021-10-30 10:34 ` Eli Zaretskii
2021-10-30 17:13 ` Vince Salvino
2021-10-30 17:39 ` Eli Zaretskii
2021-11-11 5:36 ` bug#47291: " Lars Ingebrigtsen
2021-11-11 7:51 ` Eli Zaretskii
2021-11-11 12:15 ` Lars Ingebrigtsen
2021-11-11 15:08 ` Eli Zaretskii
2021-11-12 3:00 ` Lars Ingebrigtsen
2021-11-12 6:19 ` Eli Zaretskii [this message]
2022-01-14 6:00 ` Vince Salvino
2022-01-23 0:00 ` Vince Salvino
2022-01-29 3:34 ` bug#51404: " Vince Salvino
2022-01-29 8:40 ` bug#51404: " Eli Zaretskii
2022-01-29 20:27 ` Vince Salvino
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=83k0hdzyj9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=47291@debbugs.gnu.org \
--cc=51404@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=salvino@coderedcorp.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).