unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 27357@debbugs.gnu.org
Subject: bug#27357: 26.0.50; Emacs starts fullscreen in Ubuntu 17.04
Date: Wed, 14 Jun 2017 23:50:30 +0200	[thread overview]
Message-ID: <m38tkuutll.fsf@stories> (raw)
In-Reply-To: <594143AB.7040500@gmx.at> (martin rudalics's message of "Wed, 14 Jun 2017 16:09:47 +0200")

I'm having a hard time making sense of the code flow in xterm.c.  But
what seems to be happening is that Emacs first comes up with a frame in
proper size, and then it's rescaled to be fullsize.

Looking at get_current_wm_state, in that loop there, a matches both
dpyinfo->Xatom_net_wm_state_maximized_horz and
dpyinfo->Xatom_net_wm_state_maximized_vert, which explains why Emacs
gets maximized.

But I'm having no luck in understanding why those fields are being set,
or where...

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no






  parent reply	other threads:[~2017-06-14 21:50 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-14 12:33 bug#27357: 26.0.50; Emacs starts fullscreen in Ubuntu 17.04 Lars Ingebrigtsen
2017-06-14 14:09 ` martin rudalics
2017-06-14 16:38   ` Lars Ingebrigtsen
2017-06-14 17:00     ` Eli Zaretskii
2017-06-14 17:08       ` Lars Ingebrigtsen
2017-06-15  7:59     ` martin rudalics
2017-06-15  9:07       ` Lars Ingebrigtsen
2017-06-15 10:08         ` martin rudalics
2017-06-14 21:50   ` Lars Ingebrigtsen [this message]
2017-06-14 22:08     ` Lars Ingebrigtsen
2017-06-15  7:59       ` martin rudalics
2017-06-15  9:11         ` Lars Ingebrigtsen
2017-06-15  9:23           ` Lars Ingebrigtsen
2017-06-15 10:11             ` martin rudalics
2017-07-05 19:42               ` Lars Ingebrigtsen
2017-07-05 20:12                 ` Lars Ingebrigtsen
2017-07-06  6:30                   ` martin rudalics
2017-07-16 12:40                     ` Lars Ingebrigtsen
2017-07-16 12:51                       ` martin rudalics
2017-07-16 13:04                         ` Lars Ingebrigtsen
2017-07-16 13:29                           ` Lars Ingebrigtsen
2017-07-16 13:34                           ` Lars Ingebrigtsen
2017-07-16 13:45                             ` Lars Ingebrigtsen
2017-07-16 13:55                               ` martin rudalics
2017-07-16 13:59                                 ` Lars Ingebrigtsen
2017-07-16 14:10                                   ` martin rudalics
2017-07-16 14:27                                     ` Lars Ingebrigtsen
2017-07-16 15:05                                       ` Lars Ingebrigtsen
2017-07-16 15:09                                         ` Lars Ingebrigtsen
2017-07-16 16:39                                           ` Dmitry Gutov
2017-07-16 16:49                                             ` Lars Ingebrigtsen
2017-07-17 14:04                                               ` Robert Pluim
2017-07-17 15:00                                                 ` Lars Ingebrigtsen
2017-07-17 15:16                                                   ` Lars Ingebrigtsen
2017-07-16 15:16                                       ` Lars Ingebrigtsen
2017-07-16 16:11                                         ` Lars Ingebrigtsen
2017-07-17  7:03                                           ` martin rudalics
2017-07-16 14:19                                   ` Eli Zaretskii
2017-07-16 14:03                                 ` Lars Ingebrigtsen
2017-07-16 13:54                             ` martin rudalics
2017-06-15 10:09           ` martin rudalics

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=m38tkuutll.fsf@stories \
    --to=larsi@gnus.org \
    --cc=27357@debbugs.gnu.org \
    --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).