unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Maximiliano Sandoval <msandova@protonmail.com>
Cc: 53457@debbugs.gnu.org
Subject: bug#53457: 29.0.50; pgtk: [Request] Expose GtkSettings to emacs
Date: Sun, 23 Jan 2022 09:39:44 +0800	[thread overview]
Message-ID: <875yqbtelb.fsf@yahoo.com> (raw)
In-Reply-To: <s_AAaWFCNcERrAQtMv8FjaEeGlb8Jtg6mF6E11VVOi8Bz_xHeT3Mnudz_Wx-DLRzZMg5uAZZPFm3iYTex_dngOlbPCWWlFy7QKwZiY36n0s=@protonmail.com> (Maximiliano Sandoval's message of "Sat, 22 Jan 2022 21:32:37 +0000")

Maximiliano Sandoval <msandova@protonmail.com> writes:

> 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.

We don't have a "proper GTK header bar", only the fallback title bar GTK
uses for window decoration, which is only available on window systems
where server side decorations don't exist (such as Wayland and
Broadway.)

In addition to that, the setting is deprecated, so I think relying on it
to set the stylesheet used for window decorations will not be very
effective.

People will probably start screaming like goats if we enable the
fallback title bar on X as well, since client-side decorations are a
very controversial subject, so the best option would be to utilize the
system-wide settings for that job.

Thanks.





  reply	other threads:[~2022-01-23  1:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-22 21:32 bug#53457: 29.0.50; pgtk: [Request] Expose GtkSettings to emacs Maximiliano Sandoval via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-23  1:39 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
     [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=875yqbtelb.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=53457@debbugs.gnu.org \
    --cc=luangruo@yahoo.com \
    --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).