From: martin rudalics <rudalics@gmx.at>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 45737@debbugs.gnu.org
Subject: bug#45737: 27.1.50; Assertion failure in window_box_height
Date: Sun, 10 Jan 2021 17:06:36 +0100 [thread overview]
Message-ID: <bc3e68cc-34da-727d-ff37-1b70dd427574@gmx.at> (raw)
In-Reply-To: <83h7nqgci6.fsf@gnu.org>
> I'm okay with the frame resetting itself back to a safe size, if the
> WM cannot be hinted.
We can try to hint the WM and even make that the default. But this
won't help people on tiling WMs or embedded frames. And a WM that
cannot be hinted might just size the frame back as well. We had some
issues with GNOME shell in the past and with pgtk/Wayland most of our
desires to control screen layout will have become a pipe dream anyway.
> The main point is not to reduce the frame size
> to dimensions that don't allow us to keep a mini-window of at least
> one line.
It depends on what _we_ want to show above that line. The screen estate
within the native frame rectangle is and will stay with us forever.
martin
next prev parent reply other threads:[~2021-01-10 16:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-09 9:33 bug#45737: 27.1.50; Assertion failure in window_box_height martin rudalics
2021-01-09 10:00 ` Eli Zaretskii
2021-01-09 10:28 ` martin rudalics
2021-01-09 11:43 ` Eli Zaretskii
2021-01-09 17:06 ` martin rudalics
2021-01-09 17:25 ` martin rudalics
2021-01-09 17:49 ` Eli Zaretskii
2021-01-09 18:48 ` martin rudalics
2021-01-09 19:02 ` Eli Zaretskii
2021-01-10 16:06 ` martin rudalics [this message]
2022-02-07 1:05 ` Lars Ingebrigtsen
2022-02-07 8:57 ` 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
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=bc3e68cc-34da-727d-ff37-1b70dd427574@gmx.at \
--to=rudalics@gmx.at \
--cc=45737@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).