unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: storm@cua.dk (Kim F. Storm)
Cc: "Marshall, Simon" <simon.marshall@misys.com>,
	"'emacs-devel@gnu.org'" <emacs-devel@gnu.org>
Subject: Re: [simon.marshall@misys.com: Detached minibuffer cropped text]
Date: Tue, 20 Jun 2006 10:53:25 +0200	[thread overview]
Message-ID: <m3bqsow6m2.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <85d5d45nu8.fsf@lola.goethe.zz> (David Kastrup's message of "Tue, 20 Jun 2006 08:43:27 +0200")

David Kastrup <dak@gnu.org> writes:

> storm@cua.dk (Kim F. Storm) writes:
>
>> "Marshall, Simon" <simon.marshall@misys.com> writes:
>>
>>> Hi Kim, that does sound quite right either - the minibuffer frame is
>>> specified to have a height of 1, but you see 2 lines.  Or are you including
>>> the WM title bar?
>>
>> The display engine requires that window height is an whole multiple of
>> the default frame line height.  So if 1 line is not enough, the next
>> choice is 2 lines.
>>
>> I don't know why Emacs selects one line in your case, and 2 lines in my
>> case.  It could be some property of the font -- I don't know.
>
> Could be that the mode line font (or the minibuffer font after
> font-lock) in one case is larger than one line of the default font,
> and in one case isn't.

It must be a dicision made during frame creation, i.e. before any text
is displayed in the minibuffer window (which is the only window in the
detached minibuffer frame.

So in my case, the frame is created with two lines, in Simon's case it
is created with one line.  Depending on the point of view, both
behaviours may be correct, but the question is what controls this.

-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk

  reply	other threads:[~2006-06-20  8:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-19 10:13 [simon.marshall@misys.com: Detached minibuffer cropped text] Marshall, Simon
2006-06-19 22:01 ` Kim F. Storm
2006-06-20  6:43   ` David Kastrup
2006-06-20  8:53     ` Kim F. Storm [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-08-10 12:18 Marshall, Simon
2006-06-22 11:19 Marshall, Simon
2006-06-20  8:50 Marshall, Simon
2006-06-17 17:58 Richard Stallman
2006-06-18 21:12 ` Kim F. Storm

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=m3bqsow6m2.fsf@kfs-l.imdomain.dk \
    --to=storm@cua.dk \
    --cc=emacs-devel@gnu.org \
    --cc=simon.marshall@misys.com \
    /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).