From: Stefan Kangas <stefankangas@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>,
"Rahul M. Juliato" <rahuljuliato@gmail.com>
Cc: 68766@debbugs.gnu.org
Subject: bug#68766: 29.2; Windows dark/light mode changes does not reflect on Emacs Title bar/Scrollbar
Date: Mon, 29 Jan 2024 17:34:54 -0500 [thread overview]
Message-ID: <CADwFkmnhf4vzBJ2u91ZAvxL0q+cSz4tKsxgRQRzBxAGUmK9NfQ@mail.gmail.com> (raw)
In-Reply-To: <86y1ca55er.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
> It's "by design", in the sense that this is how the Dark theme support
> is implemented in Emacs. If someone submits changes to react to theme
> change immediately for all the frames, we can consider that for
> inclusion.
I think that would be a useful feature, indeed.
AFAIU, the point of light/dark mode for many users is that they want to
use different settings depending on the time of day. This needs the
Emacs frame to react to it when the time switches (as most programs in
desktop environments like Gnome, or even macOS, do).
For example, Emacs on macOS already reacts automatically to light/dark
mode settings. I believe this is provided by the toolkit itself,
without any changes in Emacs (or I missed them going in).
---
On a side note, I still don't think we have support for changing the
theme as well, do we? This is the feature that auto-dark-mode provides.
In addition to changing the toolbar settings, I'd propose the new user
options `theme-dark' and `theme-light' indicating themes to switch to
when the desktop environment tells us that it's time.
This would be possible if the above new feature could also expose these
events to Lisp somehow.
next prev parent reply other threads:[~2024-01-29 22:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-28 2:08 bug#68766: 29.2; Windows dark/light mode changes does not reflect on Emacs Title bar/Scrollbar Rahul M. Juliato
2024-01-28 2:40 ` Stefan Kangas
2024-01-28 6:42 ` Eli Zaretskii
2024-01-30 19:52 ` Rahul M. Juliato
2024-01-28 6:38 ` Eli Zaretskii
2024-01-29 22:34 ` Stefan Kangas [this message]
2024-01-30 7:37 ` Visuwesh
2024-01-30 11:57 ` Rudolf Schlatte
2024-01-30 13:15 ` Eli Zaretskii
2024-01-30 19:57 ` Rahul M. Juliato
2024-02-03 9:57 ` Eli Zaretskii
2024-02-19 1:15 ` Rahul M. Juliato
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=CADwFkmnhf4vzBJ2u91ZAvxL0q+cSz4tKsxgRQRzBxAGUmK9NfQ@mail.gmail.com \
--to=stefankangas@gmail.com \
--cc=68766@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=rahuljuliato@gmail.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).