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: Sat, 9 Jan 2021 19:48:32 +0100 [thread overview]
Message-ID: <9f684e70-0195-e2a1-fccf-bed4b2e8ad1c@gmx.at> (raw)
In-Reply-To: <83pn2egfuj.fsf@gnu.org>
>> That would be better indeed. But I suppose this would require to
>> implement zero-height windows, something you didn't like when we
>> discussed it about a year ago.
>
> 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".
But maybe I'm missing something.
martin
next prev parent reply other threads:[~2021-01-09 18:48 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 [this message]
2021-01-09 19:02 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9f684e70-0195-e2a1-fccf-bed4b2e8ad1c@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 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.