From: Juri Linkov <juri@linkov.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 37609@debbugs.gnu.org
Subject: bug#37609: Tool-bar-mode grows the frame's height
Date: Sun, 06 Oct 2019 01:44:18 +0300 [thread overview]
Message-ID: <87a7aeu7l1.fsf@mail.linkov.net> (raw)
In-Reply-To: <83r23r2eug.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 05 Oct 2019 22:04:55 +0300")
>> 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?
Since there is no such problem on GTK builds that use external tool-bars,
maybe it's ok that this behavior is only on Lucid, Motif, Windows?
next prev parent reply other threads:[~2019-10-05 22:44 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 [this message]
[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
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=87a7aeu7l1.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=37609@debbugs.gnu.org \
--cc=eliz@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).