unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Clément Pit--Claudel" <clement.pit@gmail.com>
To: martin rudalics <rudalics@gmx.at>,
	23925@debbugs.gnu.org, Roland Winkler <winkler@gnu.org>
Subject: bug#23925: 25.0.95; display broken when maximizing frame
Date: Mon, 11 Jul 2016 19:47:11 +0200	[thread overview]
Message-ID: <5783DB9F.9000104@gmail.com> (raw)
In-Reply-To: <5783635B.2030602@gmx.at>


[-- Attachment #1.1: Type: text/plain, Size: 1640 bytes --]

On 2016-07-11 11:14, martin rudalics wrote:
> All these values are as expected - I suppose that they are the same as
> in a non-cairo GTK session.  What happens when you type F11
> (‘toggle-frame-fullscreen’) in a normal frame?  Also, could one of you
> try a Lucid or Motif build with cairo and see what happens?

F11 in a non-cairo session works fine; in a cairo one, it shows exactly the same problem.

In a non-cairo build, I get:

((outer-position 0 . 0) (outer-size 1920 . 1055) (external-border-size 0 . 1) (title-bar-size 0 . 23) (menu-bar-external . t) (menu-bar-size 1920 . 22) (tool-bar-external . t) (tool-bar-position . top) (tool-bar-size 1920 . 44) (internal-border-width . 0))

frame pixel: 1920 x 964   cols/lines: 240 x 56   units: 8 x 17
frame text pixel: 1891 x 964   cols/lines: 236 x 56
tool: 0  scroll: 13/0  fringe: 16  border: 0  right: 0  bottom: 0

#<window 3 on *scratch*>   parent: nil
pixel left: 0   top: 0   size: 1920 x 930   new: 947
char left: 0   top: 0   size: 240 x 54   new: 54
normal: 1.0 x 1.0   new: nil
body pixel: 1891 x 913   char: 236 x 53
width left fringe: 8  left margin: 0  right margin: 0
width right fringe: 8  scroll-bar: 13  divider: 0
height header-line: 0  mode-line: 17  divider: 0

#<window 4 on  *Minibuf-0*>   parent: nil
pixel left: 0   top: 930   size: 1920 x 34   new: 0
char left: 0   top: 54   size: 240 x 2   new: 1
normal: 1.0 x 1.0   new: 0
body pixel: 1891 x 34   char: 236 x 2
width left fringe: 8  left margin: 0  right margin: 0
width right fringe: 8  scroll-bar: 13  divider: 0
height header-line: 0  mode-line: 0  divider: 0



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2016-07-11 17:47 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-09  3:02 bug#23925: 25.0.95; display broken when maximizing frame Roland Winkler
2016-07-09  7:11 ` Eli Zaretskii
2016-07-09  9:45   ` Clément Pit--Claudel
2016-07-09 15:30     ` martin rudalics
2016-07-10  1:52       ` Clément Pit--Claudel
2016-07-11  9:14         ` martin rudalics
2016-07-11 17:47           ` Clément Pit--Claudel [this message]
2016-07-12  7:29             ` martin rudalics
2016-07-12  9:29               ` Clément Pit--Claudel
2016-07-13 14:58               ` Roland Winkler
2016-07-13 17:34                 ` martin rudalics
2018-11-22 14:12     ` Dmitry Gutov
2018-12-11  1:40       ` Dmitry Gutov
2018-12-17 19:28         ` Clément Pit-Claudel
2019-03-26  2:12           ` YAMAMOTO Mitsuharu
2019-06-18 20:03           ` Clément Pit-Claudel
2019-06-18 21:33             ` Dmitry Gutov
2019-06-19  0:26               ` YAMAMOTO Mitsuharu
2019-06-19  1:22                 ` Dmitry Gutov
2019-06-19  1:38                   ` YAMAMOTO Mitsuharu
2019-06-19  1:48                     ` Dmitry Gutov
2019-06-19 14:07                     ` Clément Pit-Claudel
2019-06-21  0:36                       ` YAMAMOTO Mitsuharu
2019-06-19  3:31                   ` Roland Winkler
2019-06-18 23:52             ` YAMAMOTO Mitsuharu
2018-12-11  3:36     ` Dmitry Gutov
2018-12-11  8:49       ` Robert Pluim
2016-07-09 21:05   ` Roland Winkler
2016-07-09  9:20 ` martin rudalics
2016-07-09 17:32 ` Glenn Morris
2016-07-09 17:42   ` Eli Zaretskii
2016-07-10  1:03     ` Glenn Morris
2016-07-10 14:27       ` Eli Zaretskii
2016-07-15 15:46         ` Roland Winkler
2016-07-15 16:04           ` Eli Zaretskii
2016-07-23 17:44           ` 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=5783DB9F.9000104@gmail.com \
    --to=clement.pit@gmail.com \
    --cc=23925@debbugs.gnu.org \
    --cc=rudalics@gmx.at \
    --cc=winkler@gnu.org \
    /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).