From: martin rudalics <rudalics@gmx.at>
To: david@ngdr.net
Cc: "25943@debbugs.gnu.org" <25943@debbugs.gnu.org>
Subject: bug#25943: 21.5 Frame Display Difficulties
Date: Tue, 04 Apr 2017 09:25:47 +0200 [thread overview]
Message-ID: <58E34A7B.70103@gmx.at> (raw)
In-Reply-To: <a953a429ef4b6552445b6f2c8d9e4c2f@127.0.0.1>
> (frame-edges frame 'outer=edges)
'outer-edges please
> (599 256 1431 940) (599 256 1431 940) (599 256 1431 940))
The first value looks wrong supposedly due to the outer=edges mishap.
> ;; Immediately after maximizing by clicking on the top-right +. Note that
> the value of frame is
> ;; different.
> frame
> #<frame *scratch* 0x131b0b0>
That's normal. The notation is cryptic but people are fond of it.
However, these values
> (outer-size 2048 .
> 1114)
...
> (0 100 2048 1151) (0 100 2048 1151) (0 100 2048 1151))
sampled from GTK clearly mismatch those of the Emacs window management
routines
> frame pixel: 832 x 684 cols/lines: 84 x 36 units: 10 x 19
> frame text pixel: 800 x 684 cols/lines: 80 x 36
and represent what you see on your images: A window manager window of
2048 x 1114 pixels and an embedded Emacs frame of 832 x 684 pixels. The
size has not propagated properly.
> ;; Just after obtaining the information above the (real, not reported)
> workarea expanded to its
> ;; "proper" maximized size with no intentional input from me. I ran the
> checks again, and the
> ;; results are different.
Now
> (outer-size 2048 .
> 1114)
...
> (0 100 2048 1151) (0 100 2048 1151) (0 100 2048 1151))
are as before but
> frame pixel: 2048 x 1051 cols/lines: 205 x 55 units: 10 x 19
> frame text pixel: 2016 x 1051 cols/lines: 201 x 55
show that Emacs caught up with GTK. What happens when you click the ‘+’
button three times in a row? BTW, I suppose that this behavior shows up
only in your ssh setup and you cannot repeat it without tunneling. Do
you observe a similar behavior via ssh when you substantially change the
frame size via ‘set-frame-size’?
Also, did you try the ssh experiment with your 23.2 build? And it would
be interesting if you were able to reproduce the behavior with a 25.2 Lucid
or Motif build.
> ;; I started a new emacs and ran (setq frame (make-frame '((tool-bar-lines
> . 0))) ). Then I set the
> ;; fullscreen parameter with results indicated below.
>
> (set-frame-parameter frame 'fullscreen 'maximized)
> ;; The outersize changed to fullscreen, the (real) workarea did not change
> in size, but it did
> ;; relocate to Left Top. In other words the result was very similar to a
> normal, problem, start.
>
> (set-frame-parameter frame 'fullscreen 'fullboth)
> ;; From the position above, this caused the outerframe to increase in
> size, eliminating the frame
> ;; border. The workarea moved, further Left Top, but did not change in
> size.
With other words the behavior is the same regardless of whether you use
`set-frame-parameter', M-F10 or the ‘+’ button on the title bar.
> (set-frame-parameter frame 'fullscreen 'fullheight)
> (set-frame-parameter frame 'fullscreen 'fullwidth)
> ;; I have never used these, so I do not know how they are intended to
> work. After these, the shape
> ;; changed to fullheight and fullwidth, respectively. The other dimension
> changed to the width and
> ;; height of the workarea and the whole outershape moved so that it was
> centered horizontally and
> ;; vertically respectively. The attached screenshot shows one of these
> configurations.
I can't tell about these because you haven't included the
‘frame-geometry’ output but I suppose they won't tell us anything new.
Thanks, martin
next prev parent reply other threads:[~2017-04-04 7:25 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 3:51 bug#25943: 21.5 Frame Display Difficulties david
2017-03-03 8:13 ` martin rudalics
[not found] ` <af552a322a8a630796cbddf1133b6dbe@127.0.0.1>
2017-03-04 9:59 ` martin rudalics
2017-03-07 1:51 ` david
2017-03-07 9:45 ` martin rudalics
2017-03-08 22:58 ` david
2017-03-09 8:56 ` martin rudalics
2017-03-10 18:44 ` david
2017-03-11 10:21 ` martin rudalics
2017-03-23 7:59 ` martin rudalics
2017-03-28 22:43 ` david
2017-03-29 7:36 ` martin rudalics
2017-03-29 19:53 ` david
2017-03-30 7:29 ` martin rudalics
2017-04-01 4:35 ` david
2017-04-01 7:36 ` martin rudalics
[not found] ` <7ee8200b866d8067514fb8b0bb9e814b@127.0.0.1>
2017-04-02 7:55 ` martin rudalics
2017-04-04 0:35 ` david
2017-04-04 7:25 ` martin rudalics [this message]
2017-04-07 0:12 ` david
2017-04-07 5:56 ` martin rudalics
2017-04-07 21:16 ` david
2022-04-25 14:48 ` Lars Ingebrigtsen
2022-05-24 12:50 ` Lars Ingebrigtsen
2017-04-07 21:19 ` david
2017-04-08 9:00 ` martin rudalics
2017-04-11 6:49 ` 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=58E34A7B.70103@gmx.at \
--to=rudalics@gmx.at \
--cc=25943@debbugs.gnu.org \
--cc=david@ngdr.net \
/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.