From: Juri Linkov <juri@linkov.net>
To: martin rudalics <rudalics@gmx.at>
Cc: 37609@debbugs.gnu.org
Subject: bug#37609: Tool-bar-mode grows the frame's height
Date: Wed, 05 May 2021 00:42:40 +0300 [thread overview]
Message-ID: <87y2cub2gf.fsf@mail.linkov.net> (raw)
In-Reply-To: <507f8fc7-651a-12ea-20e6-bf2092ab5ed1@gmx.at> (martin rudalics's message of "Tue, 4 May 2021 11:15:58 +0200")
> Revisiting after some recent changes:
>
>> emacs -Q -f tool-bar-mode
>>
>> that disables tool-bar-mode before it's displayed for the first time,
>> and evaluating
>>
>> (let ((initial (assq 'outer-size (frame-geometry))))
>> (tool-bar-mode 1)
>> (tool-bar-mode 0)
>> (list (assq 'outer-size (frame-geometry)) initial))
>>
>> => ((outer-size 680 . 693) (outer-size 680 . 676))
>>
>> indicates growing of the frame's height.
>
> Here I get with a current Lucid (I suppose you will encounter troubles
> building with Motif these days) build
>
> ((outer-size 764 . 702) (outer-size 764 . 702))
>
> whereas on Emacs 27 this was indeed
>
> ((outer-size 764 . 720) (outer-size 764 . 702))
>
> Can you please check again?
Now the frame's height doesn't grow but shrinks on GTK:
((outer-size 694 . 690) (outer-size 694 . 738))
>> OTOH, in a new session again with emacs -Q -f tool-bar-mode
>>
>> (progn
>> (tool-bar-mode 1)
>> (assq 'outer-size (frame-geometry)))
>>
>> => (outer-size 680 . 693)
>
> This gets me
>
> (outer-size 764 . 720)
(outer-size 694 . 690)
> but evaluating
>
> (assq 'outer-size (frame-geometry))
>
> once more (it takes time to relate such changes to `frame-geometry') now
> gives
>
> (outer-size 764 . 738)
(outer-size 694 . 738)
> which should yield the same value of (frame-height) as before (please
> check).
(frame-height)
36
> On Emacs 27 this was botched because the outer size changed to
>
> (outer-size 764 . 720)
>
> only and the frame height dropped from 36 to 35 lines.
>
>> (progn
>> (tool-bar-mode 0)
>> (assq 'outer-size (frame-geometry)))
>>
>> => (outer-size 680 . 693)
>
> This now gets me
>
> (outer-size 764 . 702)
>
> as expected.
(outer-size 694 . 690)
>> It's strange that the results are the same because visually
>> the frame's height grows.
> So please have one more look into this issue.
Do you think now it's improved?
next prev parent reply other threads:[~2021-05-04 21:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-03 22:20 bug#37609: Tool-bar-mode grows the frame's height Juri Linkov
2019-10-05 8:41 ` martin rudalics
2019-10-05 18:11 ` martin rudalics
2019-10-05 19:04 ` Eli Zaretskii
2019-10-05 22:44 ` Juri Linkov
[not found] ` <626bf59c-99e7-b6ac-5e0e-7493d214d4e2@gmx.at>
2022-01-24 18:03 ` Juri Linkov
2021-05-04 9:15 ` martin rudalics
2021-05-04 21:42 ` Juri Linkov [this message]
2021-05-05 7:24 ` martin rudalics
2021-05-05 20:37 ` Juri Linkov
2021-05-06 7:45 ` martin rudalics
2021-05-07 16:50 ` Juri Linkov
2021-05-08 7:16 ` martin rudalics
2021-05-08 20:23 ` Juri Linkov
2021-05-09 8:41 ` martin rudalics
2021-05-09 17:43 ` Juri Linkov
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=87y2cub2gf.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=37609@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).