From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Michael Heerdegen <michael_heerdegen@web.de>, 24293@debbugs.gnu.org
Subject: bug#24293: 25.1; Display bug: icomplete prompt not visible with icomplete-separator "\n"
Date: Sat, 19 Sep 2020 13:47:12 -0400 [thread overview]
Message-ID: <jwvbli1bqyw.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83d1kzfogn.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 23 Aug 2016 19:18:48 +0300")
>> In emacs -Q, eval
>>
>> (setq icomplete-separator "\n")
>>
>> and do
>>
>> M-x icomplete-mode <return>
>>
>> Then, e.g.
>>
>> M-x m
>>
>> The icomplete minibuffer prompt is invisible (bug).
>>
>> But you see that it's "there" when you hit <left>. And changing the
>> value of `resize-mini-windows' to nil makes the issue disappear - so I
>> think this is caused by a problem in the display code.
>
> Surprisingly, stepping through the code with a debugger reveals that
> this is not a bug, but (almost) deliberate behavior. Set
> max-mini-window-height to 0.9, and you will see the entire prompt.
The "prompt" in the above example is not the whole text shown in the
minibuffer but just "M-x m".
> The default value of that variable is 0.25, so Emacs doesn't resize
> mini-windows to more than 1/4th of the height of the frame's root
> window. And the height required to show the prompt is much larger in
> this case.
No, a single line is sufficient to show "the prompt".
Stefan
next prev parent reply other threads:[~2020-09-19 17:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 15:44 bug#24293: 25.1; Display bug: icomplete prompt not visible with icomplete-separator "\n" Michael Heerdegen
2016-08-23 16:18 ` Eli Zaretskii
2016-08-23 19:06 ` Michael Heerdegen
2016-08-23 19:38 ` Drew Adams
2016-08-24 2:44 ` Eli Zaretskii
2016-08-24 2:47 ` Eli Zaretskii
2016-08-24 9:08 ` martin rudalics
2020-09-19 17:47 ` Stefan Monnier [this message]
2020-04-05 12:42 ` Dmitry Gutov
2020-04-05 12:56 ` Dmitry Gutov
2020-12-04 11:08 ` Lars Ingebrigtsen
2020-12-08 0:08 ` Michael Heerdegen
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=jwvbli1bqyw.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=24293@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=michael_heerdegen@web.de \
/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).