From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 46963@debbugs.gnu.org
Subject: bug#46963: 28.0.50; Bad WM size hints in GTK-3 builds
Date: Sat, 06 Mar 2021 22:13:32 +0200 [thread overview]
Message-ID: <837dmkujkj.fsf@gnu.org> (raw)
In-Reply-To: <a517ad67-9acc-8ee7-2340-0b8debf15a52@gmx.at> (message from martin rudalics on Sat, 6 Mar 2021 20:29:02 +0100)
> Cc: 46963@debbugs.gnu.org
> From: martin rudalics <rudalics@gmx.at>
> Date: Sat, 6 Mar 2021 20:29:02 +0100
>
> > Alternatively, we could disallow making frames smaller than 4 lines,
> > because making our code jump through hoops for uses cases that are
> > supposed to be rare, to say the least, makes little sense to me.
>
> That's what I'm trying to do because you asked for such a solution. It
> cannot be a fixed number of lines like 4 because minibuffer-only or
> ediff control frames want less. OTOH four lines are not enough when
> shrinking a frame with say four windows stacked above each other.
>
> Rather, I calculate, from the number of vertically stacked windows, the
> presence of scroll bars, mode, header and tab bar lines and a plethora
> of other factors a minimal height of the frame and try to pass that to
> the window manager. But GTK3 intercepts me.
Then perhaps we should document this oddity in PROBLEMS and forget
about it.
next prev parent reply other threads:[~2021-03-06 20:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-06 10:47 bug#46963: 28.0.50; Bad WM size hints in GTK-3 builds martin rudalics
2021-03-06 11:04 ` Eli Zaretskii
2021-03-06 19:29 ` martin rudalics
2021-03-06 20:13 ` Eli Zaretskii [this message]
2021-03-08 8:25 ` 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=837dmkujkj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=46963@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 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.