unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Markus Triska <triska@metalevel.at>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 67715@debbugs.gnu.org
Subject: bug#67715: 28.2; Minibuffer content is sometimes unexpectedly partially hidden
Date: Sat, 09 Dec 2023 08:04:40 +0100	[thread overview]
Message-ID: <874jgrvotz.fsf@metalevel.at> (raw)
In-Reply-To: <838r64zb3r.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 08 Dec 2023 22:35:20 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

> Why did you expect the mini-window to resize in this case?

The Emacs Lisp documentation states in section 21.1:

    The minibuffer’s window is normally a single line; it grows
    automatically if the contents require more space.

I therefore expected it to grow automatically in the case I posted,
especially also because this is done in many Emacs versions before 28.2,
such as 26.1, 26.2, 26.3, 27.1, 27.2 and 28.1.

> find another way of ensuring the enlarged text is visible, in your
>
I added (fit-window-to-buffer) after inserting the text, and still the
text is not fully visible. fit-window-to-buffer is documented as:

    Adjust size of WINDOW to display its buffer’s contents exactly.

I would greatly prefer if Emacs works as documented. Should I file a
separate issue for this, or is this also a case of wontfix? Is there any
way to solve the issue?

Thank you a lot!
Markus





  reply	other threads:[~2023-12-09  7:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-08 19:03 bug#67715: 28.2; Minibuffer content is sometimes unexpectedly partially hidden Markus Triska
2023-12-08 20:35 ` Eli Zaretskii
2023-12-09  7:04   ` Markus Triska [this message]
2023-12-09  7:59     ` Eli Zaretskii
2023-12-09  9:04       ` Markus Triska
2023-12-09 11:18         ` Eli Zaretskii
2023-12-10  8:12           ` Markus Triska
2023-12-10  9:27             ` Eli Zaretskii
2023-12-11 17:12           ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-14  7:43             ` Markus Triska
2024-01-14  8:49               ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-09 17:02         ` Eli Zaretskii
2023-12-09 20:09           ` Markus Triska
2023-12-09 20:20             ` Eli Zaretskii
2023-12-09 21:11               ` Markus Triska
2023-12-10  5:44                 ` Eli Zaretskii
2023-12-10 17:59                   ` Markus Triska

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=874jgrvotz.fsf@metalevel.at \
    --to=triska@metalevel.at \
    --cc=67715@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).