From: Carlos Pita <carlosjosepita@gmail.com>
To: martin rudalics <rudalics@gmx.at>
Cc: 31968@debbugs.gnu.org, Robert Pluim <rpluim@gmail.com>,
Jonathan Kyle Mitchell <kyle@jonathanmitchell.org>
Subject: bug#31968: 26.1.50; Allow to hide title bar on maximize (gtk/gnome/csd)
Date: Sun, 1 Jul 2018 14:35:56 -0300 [thread overview]
Message-ID: <CAELgYhe-ras=WThgVJdTn2ziyEJwPn=1eoCYUkJcEq2u-4ftoA@mail.gmail.com> (raw)
In-Reply-To: <CAELgYhfUL1JscWX2MSY+A2tO2-+=Wi4ZtXSooXnPDQtrVB-2QQ@mail.gmail.com>
It could be a matter of timing since sometimes (ii->iii) indeed
restores the decorations, but most of the time it doesn't.
Also I realized that the above is more simple and reliable to
reproduce by just pressing Alt-F10 twice (toggle maximized on/off),
when restoring the normal window size it doesn't get its decorations
again. I would say that this also is a timing issue, because xprop
correctly shows that the x11 window is not maximized but emacs thinks
otherwise, probably because an emacs window was resized before the x11
window properties were set by the wm.
next prev parent reply other threads:[~2018-07-01 17:35 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
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 [this message]
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='CAELgYhe-ras=WThgVJdTn2ziyEJwPn=1eoCYUkJcEq2u-4ftoA@mail.gmail.com' \
--to=carlosjosepita@gmail.com \
--cc=31968@debbugs.gnu.org \
--cc=kyle@jonathanmitchell.org \
--cc=rpluim@gmail.com \
--cc=rudalics@gmx.at \
/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).