unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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 13:43:39 +0200	[thread overview]
Message-ID: <83zh1igwt0.fsf@gnu.org> (raw)
In-Reply-To: <8d247025-528e-00a7-b92a-c59c775f6968@gmx.at> (message from martin rudalics on Sat, 9 Jan 2021 11:28:06 +0100)

> Cc: 45737@debbugs.gnu.org
> From: martin rudalics <rudalics@gmx.at>
> Date: Sat, 9 Jan 2021 11:28:06 +0100
> 
>  > What happens in the above scenario with your patch installed?
> 
> What Emacs is asking for in the scenario is to enlarge the minibuffer
> window (for whatever reason, I didn't care).  With the patch installed,
> Emacs won't do that but keep the minibuffer window size alone.  Note
> that for the assertion failure to trigger here, the minibuffer window
> must not be visible already.

So the frame will resize as result dragging by mouse, but the
mini-window will not be visible?

If that is the effect, then I'm okay with installing this on emacs-27,
but I wonder whether we could do better on master, so as to ensure
that at least one screen line of the mini-window is still visible?

Btw, is this issue new in Emacs 27, or did it exist before?

Thanks.





  reply	other threads:[~2021-01-09 11:43 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 [this message]
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
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=83zh1igwt0.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).