From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 45737@debbugs.gnu.org
Subject: bug#45737: 27.1.50; Assertion failure in window_box_height
Date: Sat, 09 Jan 2021 21:02:09 +0200 [thread overview]
Message-ID: <83h7nqgci6.fsf@gnu.org> (raw)
In-Reply-To: <9f684e70-0195-e2a1-fccf-bed4b2e8ad1c@gmx.at> (message from martin rudalics on Sat, 9 Jan 2021 19:48:32 +0100)
> Cc: 45737@debbugs.gnu.org
> From: martin rudalics <rudalics@gmx.at>
> Date: Sat, 9 Jan 2021 19:48:32 +0100
>
> > Can you help me understand why this would mean zero-height windows?
> > What I had in mind was to constraint resizing so that the min-window
> > is always at least 1-line high.
>
> It depends on what you have in mind with "constraint resizing".
>
> - We can constraint the frame size via size hints so a user can never
> make the frame smaller than needed to make all its windows visible.
> Whether this works with other window managers depends to be seen, is
> not general practice with practically all other applications I know of
> and, as mentioned before, doesn't really work on Windows. And we
> would have to make it optional to avoid offending any users.
>
> - Otherwise we'd have to constraint the size of normal windows since
> 'window-safe-min-height' gives them always at least one frame line and
> if a frame contains two windows above each other and shrinks to two
> lines, these lines will be filled up already. So the display engine
> and/or the windows code would have to "skip" these windows to allow
> showing the minibuffer window instead. For me skipping a window is
> tantamount to giving it "zero height".
I'm okay with the frame resetting itself back to a safe size, if the
WM cannot be hinted. 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.
next prev parent reply other threads:[~2021-01-09 19:02 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 [this message]
2021-01-10 16:06 ` martin rudalics
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=83h7nqgci6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=45737@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).