unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: "Clément Pit--Claudel" <clement.pit@gmail.com>,
	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 11:14:03 +0200	[thread overview]
Message-ID: <5783635B.2030602@gmx.at> (raw)
In-Reply-To: <5781AA6D.4030803@gmail.com>

Clément:

 > (((name . "DP-2") (geometry 0 0 1920 1080) (workarea 0 0 1920 1055) (mm-size 344 193) (frames #<frame **scratch* 0x12bb5a0>) (source . "Gdk")))

 > ((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 0 . 0) (tool-bar-external . t) (tool-bar-position . top) (tool-bar-size 0 . 0) (internal-border-width . 0))

 > frame pixel: 1920 x 1030   cols/lines: 240 x 64   units: 8 x 16
 > frame text pixel: 1904 x 1030   cols/lines: 238 x 64
 > tool: 0  scroll: 0/0  fringe: 16  border: 0  right: 0  bottom: 0
 >
 > #<window 3 on *scratch*>   parent: nil
 > pixel left: 0   top: 0   size: 1920 x 1014   new: 669
 > char left: 0   top: 0   size: 240 x 63   new: 84
 > normal: 1.0 x 1.0   new: 1.0
 > body pixel: 1904 x 979   char: 238 x 61
 > width left fringe: 8  left margin: 0  right margin: 0
 > width right fringe: 8  scroll-bar: 0  divider: 0
 > height header-line: 16  mode-line: 19  divider: 0
 >
 > #<window 4 on  *Minibuf-0*>   parent: nil
 > pixel left: 0   top: 1014   size: 1920 x 16   new: 0
 > char left: 0   top: 63   size: 240 x 1   new: 84
 > normal: 1.0 x 1.0   new: ignore
 > body pixel: 1904 x 16   char: 238 x 1
 > width left fringe: 8  left margin: 0  right margin: 0
 > width right fringe: 8  scroll-bar: 0  divider: 0
 > height header-line: 0  mode-line: 0  divider: 0


Roland:

 > (((name . "DP2") (geometry 0 0 1920 1080) (workarea 0 25 1920 1055) (mm-size 510 287) (frames #<frame emacs@regnitz 0x1244a90>) (source . "Gdk")))

 > ((outer-position 0 . 25) (outer-size 1913 . 1052) (external-border-size 5 . 5) (title-bar-size 0 . 18) (menu-bar-external . t) (menu-bar-size 1903 . 22) (tool-bar-external . t) (tool-bar-position . top) (tool-bar-size 0 . 0) (internal-border-width . 1))

 > frame pixel: 1903 x 1002   cols/lines: 191 x 50   units: 10 x 20
 > frame text pixel: 1870 x 1000   cols/lines: 187 x 50
 > tool: 0  scroll: 15/0  fringe: 16  border: 1  right: 0  bottom: 0
 >
 > #<window 3 on *Messages*>   parent: nil
 > pixel left: 0   top: 0   size: 1901 x 980   new: 820
 > char left: 0   top: 0   size: 190 x 49   new: 38
 > normal: 1.0 x 1.0   new: nil
 > body pixel: 1870 x 960   char: 187 x 48
 > width left fringe: 8  left margin: 0  right margin: 0
 > width right fringe: 8  scroll-bar: 15  divider: 0
 > height header-line: 0  mode-line: 20  divider: 0
 >
 > #<window 4 on  *Minibuf-0*>   parent: nil
 > pixel left: 0   top: 980   size: 1901 x 20   new: 0
 > char left: 0   top: 49   size: 190 x 1   new: 1
 > normal: 1.0 x 1.0   new: 0
 > body pixel: 1870 x 20   char: 187 x 1
 > width left fringe: 8  left margin: 0  right margin: 0
 > width right fringe: 8  scroll-bar: 15  divider: 0
 > height header-line: 0  mode-line: 0  divider: 0


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?

martin






  reply	other threads:[~2016-07-11  9:14 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 [this message]
2016-07-11 17:47           ` Clément Pit--Claudel
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=5783635B.2030602@gmx.at \
    --to=rudalics@gmx.at \
    --cc=23925@debbugs.gnu.org \
    --cc=clement.pit@gmail.com \
    --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).