From: Maximiliano Sandoval via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 53457@debbugs.gnu.org
Subject: bug#53457: 29.0.50; pgtk: [Request] Expose GtkSettings to emacs
Date: Sat, 22 Jan 2022 21:32:37 +0000 [thread overview]
Message-ID: <s_AAaWFCNcERrAQtMv8FjaEeGlb8Jtg6mF6E11VVOi8Bz_xHeT3Mnudz_Wx-DLRzZMg5uAZZPFm3iYTex_dngOlbPCWWlFy7QKwZiY36n0s=@protonmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 392 bytes --]
Now that Emacs has a proper GTK header bar it would be interesting to
have some GtkSettings exposed, such as gtk-application-prefer-dark-theme
for example, which would allow to programmatically set dark mode for the headerbar.
Note that there are already some hacks to set the header bar to dark mode, but they depend on X11isms, see https://github.com/bepvte/gtk-variant.el.
--
Maximiliano
[-- Attachment #2: Type: text/html, Size: 1155 bytes --]
next reply other threads:[~2022-01-22 21:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-22 21:32 Maximiliano Sandoval via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-01-23 1:39 ` bug#53457: 29.0.50; pgtk: [Request] Expose GtkSettings to emacs Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <WJ317t_w4cL3_6FsmovOhAPGAzR7mgF8dBVPXM_Be5K914ayJnQz3fM53MqsZoK2HuMbcOo81HupwK9n8eCLgvynWdIVelCUlX_e04Rm8Pw=@protonmail.com>
[not found] ` <87sftfrwyr.fsf@yahoo.com>
[not found] ` <7ryBJGbLNundVwb81pO54APmKbZt-N_2vSFDHa5AgSKH7D2OvGmU-hvgtlKsNT1XxE4yCVzTI74QNro3or4CgYhOE3jaBIthrEZkA16YF-8=@protonmail.com>
2022-01-25 7:21 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-25 11:04 ` Maximiliano Sandoval via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-25 11:52 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
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='s_AAaWFCNcERrAQtMv8FjaEeGlb8Jtg6mF6E11VVOi8Bz_xHeT3Mnudz_Wx-DLRzZMg5uAZZPFm3iYTex_dngOlbPCWWlFy7QKwZiY36n0s=@protonmail.com' \
--to=bug-gnu-emacs@gnu.org \
--cc=53457@debbugs.gnu.org \
--cc=msandova@protonmail.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).