all messages for Emacs-related lists mirrored at yhetil.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, 05 Jul 2017 22:12:01 +0200	[thread overview]
Message-ID: <871spuk5im.fsf@mouse> (raw)
In-Reply-To: <87a84ik6w6.fsf@mouse> (Lars Ingebrigtsen's message of "Wed, 05 Jul 2017 21:42:17 +0200")

Oh, all this is inside Emacs.  I thought it was part of the gtk stuff
somehow.

Anyway, this is from handle_one_xevent, and this is the first of these
calls that expands the size (erroneously):

      if (!f
          && (f = any)
          && configureEvent.xconfigure.window == FRAME_X_WINDOW (f))
        {
          block_input ();
          if (FRAME_X_DOUBLE_BUFFERED_P (f))
            font_drop_xrender_surfaces (f);
          unblock_input ();
          xg_frame_resized (f, configureEvent.xconfigure.width,
                            configureEvent.xconfigure.height);

So something sets configureEvent.xconfigure.width...  And this happens
when the initial basic fonts are realised.

The call sequence here isn't completely obvious.  :-)

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






  reply	other threads:[~2017-07-05 20:12 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
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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871spuk5im.fsf@mouse \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.