From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 37609@debbugs.gnu.org, juri@linkov.net
Subject: bug#37609: Tool-bar-mode grows the frame's height
Date: Sat, 05 Oct 2019 22:04:55 +0300 [thread overview]
Message-ID: <83r23r2eug.fsf@gnu.org> (raw)
In-Reply-To: <cc1b01aa-a59b-4128-6b0b-61f817ceb90a@gmx.at> (message from martin rudalics on Sat, 5 Oct 2019 20:11:06 +0200)
> From: martin rudalics <rudalics@gmx.at>
> Date: Sat, 5 Oct 2019 20:11:06 +0200
>
> We probably could suppress such untimely growing by tricking the code
> into believing that the tool bar has already been drawn at least once
> even if it was not drawn at all. But I'm not sure whether such a
> change could break runs where showing the tool bar might be delayed
> for some reason. Getting the 'frame-inhibit-implied-resize' stuff
> perform sufficiently well was quite tricky. So is the behavior we see
> here annoying enough to warrant such a change?
As long as the behavior is consistent on all platforms, as much as
practically possible, I'm okay with this behavior. But I'm not sure
what was the conclusion regarding Juri's GTK configuration where there
was a different behavior regarding the tab bar. Was that resolved?
next prev parent reply other threads:[~2019-10-05 19:04 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83r23r2eug.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=37609@debbugs.gnu.org \
--cc=juri@linkov.net \
--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.