From: Eli Zaretskii <eliz@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 24293@debbugs.gnu.org
Subject: bug#24293: 25.1; Display bug: icomplete prompt not visible with icomplete-separator "\n"
Date: Wed, 24 Aug 2016 05:47:40 +0300 [thread overview]
Message-ID: <834m6ag9wz.fsf@gnu.org> (raw)
In-Reply-To: <87fupvxq3g.fsf@web.de> (message from Michael Heerdegen on Tue, 23 Aug 2016 21:06:11 +0200)
> From: Michael Heerdegen <michael_heerdegen@web.de>
> Cc: 24293@debbugs.gnu.org
> Date: Tue, 23 Aug 2016 21:06:11 +0200
>
> Is it possible to determine reliably the number of lines a minibuffer
> window can display maximally for given max-mini-window-height?
For a non-minibuffer frames, the calculations are in
resize_mini_window. They are quite simple, but if something there is
not clear, please ask. The documentation of max-mini-window-height in
the ELisp manual can also help.
Note that the calculations in resize_mini_window are in pixels, and a
"line height" is interpreted in terms of the frame's canonical
character height.
next prev parent reply other threads:[~2016-08-24 2: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 [this message]
2016-08-24 9:08 ` martin rudalics
2020-09-19 17:47 ` Stefan Monnier
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=834m6ag9wz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=24293@debbugs.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).