unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: David Reitter <david.reitter@gmail.com>
To: 10409@debbugs.gnu.org
Subject: bug#10409: Minibuffer sized according to default face, not minibuffer face
Date: Sat, 31 Dec 2011 10:59:53 +0100	[thread overview]
Message-ID: <561DE01C-FEF9-4EAE-A56D-A5CCFA3B92A6@gmail.com> (raw)
In-Reply-To: <BE7BBF0E-5074-4027-95E1-C2F72DEB31C8@gmail.com>

With further info from Jeremy, it looks like it works as designed.  

So would like to use this bug to request an enhancement (to allow for arbitrary (pixel level) window heights, with minibuffers sized according to the minibuffer face rather than the default face).


Begin forwarded message:

> On Fri, Dec 30, 2011 at 10:16, David Reitter <david.reitter@gmail.com> wrote:
>> I'm afraid part of this is an artifact of Emacs' long-standing way of measuring the heights of frames and windows in full glyph (or line) heights of the default face, even on post-1984 systems that have graphical user interfaces.

From: Jeremy Thurgood <firxen@gmail.com>

> Two lines (of the default face's height) are needed to display one
> line of the echo area's face. In my original case, the default face at
> 13pt was 12 pixels high (I think) and the echo area face at 13pt was
> 13 pixels high, so the minibuffer grew a second line (at the default
> face's height) for a total of 24 pixels so it could display the 13
> pixel high text without cutting any off. If there's a larger disparity
> in size, the need for multiple default-height lines in the minibuffer
> is more apparent.






  parent reply	other threads:[~2011-12-31  9:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAMH9oWq10wrpyMt4RLakT48aQMNmEQ-utXK_se4n4ooQ3DGPQw@mail.gmail.com>
2011-12-30  8:19 ` bug#10409: Minibuffer sized according to default face, not minibuffer face David Reitter
2011-12-30  9:15   ` Jeremy Thurgood
2011-12-31  9:59   ` David Reitter [this message]
2012-06-09  6:47   ` Chong Yidong
2012-06-09 10:45     ` 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=561DE01C-FEF9-4EAE-A56D-A5CCFA3B92A6@gmail.com \
    --to=david.reitter@gmail.com \
    --cc=10409@debbugs.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).