unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Michael Heerdegen <michael_heerdegen@web.de>,
	Eli Zaretskii <eliz@gnu.org>
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 11:08:01 +0200	[thread overview]
Message-ID: <57BD63F1.7070106@gmx.at> (raw)
In-Reply-To: <87fupvxq3g.fsf@web.de>

 > Is it possible to determine reliably the number of lines a minibuffer
 > window can display maximally for given max-mini-window-height?

For ‘max-mini-window-height’ specified as float you can get its maximum
theoretical pixel height by multiplying ‘max-mini-window-height’ with
the sum of the pixel heights of the frame's root window and the frame's
minibuffer window.  The real height is also constrained by the fact that
the height of the root window must not drop below the value returned by
‘window-min-pixel-height’ for that window.  Get the line value by
rounding to the pessimistic side respectively.  If you come up with a
good function, we can install it as say ‘window-max-mini-window-height’.

martin






  parent reply	other threads:[~2016-08-24  9:08 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 [this message]
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=57BD63F1.7070106@gmx.at \
    --to=rudalics@gmx.at \
    --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).