From: Robert Pluim <rpluim@gmail.com>
To: Carlos Pita <carlosjosepita@gmail.com>
Cc: 31968@debbugs.gnu.org
Subject: bug#31968: 26.1.50; Allow to hide title bar on maximize (gtk/gnome/csd)
Date: Wed, 27 Jun 2018 12:07:52 +0200 [thread overview]
Message-ID: <87fu18pmo7.fsf@gmail.com> (raw)
In-Reply-To: <877emm1trq.fsf@gmail.com> (Carlos Pita's message of "Mon, 25 Jun 2018 17:43:53 -0300")
Carlos Pita <carlosjosepita@gmail.com> writes:
> In gnome decorations are considered part of the client (even classic
> titlebars) in the sense that it's the client who decides to show them or
> not (see [1] and [2]). In waylan there is no other way around, but they
> also decided to pretend X apps behave like that. This is very frustrating
> since the reality is that many clients don't work in that way yet.
>
> So this is a request to add a gtk-hide-titlebar-if-maximized or similar
> variable since I assume emacs won't be using proper CSDs for a long
> time, maybe for good. Without that variable it's not possible to achieve
> the same humble goal in the strange new world of gnome, at least not without
> lots of xprop, xwinifo, xdotool, wmctrl, etc. horrible hacks. As I said,
> it's supposed to be the client who knows what to show and when to show
> it.
Could you explain in a bit more detail what GTK call(s) would need to
change in order to implement such a variable? That would allow us to
evaluate the effort (although personally Iʼd rather spend effort
towards implementing GTK as a native frame type).
Regards
Robert
next prev parent reply other threads:[~2018-06-27 10:07 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-25 20:43 bug#31968: 26.1.50; Allow to hide title bar on maximize (gtk/gnome/csd) Carlos Pita
2018-06-27 10:07 ` Robert Pluim [this message]
2018-06-27 13:02 ` Carlos Pita
2018-06-27 13:25 ` Robert Pluim
2018-06-27 15:20 ` Carlos Pita
2018-06-28 4:22 ` Jonathan Kyle Mitchell
2018-06-28 8:02 ` martin rudalics
2018-06-28 12:23 ` Robert Pluim
2018-06-28 8:02 ` martin rudalics
2018-06-28 15:25 ` Robert Pluim
2018-06-29 8:42 ` martin rudalics
2018-06-29 8:48 ` Robert Pluim
2018-06-30 8:33 ` martin rudalics
2018-06-30 22:32 ` Jonathan Kyle Mitchell
2018-06-30 22:54 ` Carlos Pita
2018-06-30 23:25 ` Carlos Pita
2018-07-01 0:13 ` Carlos Pita
2018-07-01 9:04 ` martin rudalics
2018-07-01 17:23 ` Carlos Pita
2018-07-01 17:35 ` Carlos Pita
2018-07-01 17:46 ` Carlos Pita
2018-07-01 18:08 ` Carlos Pita
2018-07-02 13:24 ` Robert Pluim
2018-07-02 14:28 ` Carlos Pita
2018-07-02 17:44 ` Carlos Pita
2018-07-02 20:03 ` Robert Pluim
2018-07-02 22:29 ` Carlos Pita
2018-07-03 2:06 ` Carlos Pita
2018-07-03 2:09 ` Carlos Pita
2018-07-03 23:35 ` Carlos Pita
2018-07-02 9:13 ` martin rudalics
2018-07-02 13:21 ` Robert Pluim
2018-07-01 9:02 ` martin rudalics
2018-07-02 13:31 ` Robert Pluim
2018-07-02 14:22 ` Carlos Pita
2018-07-01 9:02 ` martin rudalics
2018-07-02 5:06 ` Jonathan Kyle Mitchell
2020-09-04 4:15 ` Lars Ingebrigtsen
2022-04-28 12:03 ` Lars Ingebrigtsen
2022-04-29 4:28 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-29 10:03 ` Lars Ingebrigtsen
2022-04-29 10:25 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-29 10:31 ` Lars Ingebrigtsen
2022-04-29 10:42 ` Lars Ingebrigtsen
2022-04-29 17:11 ` Juri Linkov
2022-04-29 18:57 ` Eli Zaretskii
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=87fu18pmo7.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=31968@debbugs.gnu.org \
--cc=carlosjosepita@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).