unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
Subject: resize-mini-windows
Date: Mon, 8 Jan 2007 15:24:21 -0800	[thread overview]
Message-ID: <BDEIJAFNGDOAGCJIPKPBIENMCBAA.drew.adams@oracle.com> (raw)

1. Shouldn't user option `resize-mini-windows' be documented in Elisp manual
node Intro to Minibuffers, where the resizing is explained? That is,
shouldn't we tell users that (and how) they can control the resizing?

2. With `resize-mini-windows' = `grow-only' (the default), if I put a face
on a character in the minibuffer prompt, and the face has a :box with
1-pixel border, then the minibuffer grows about a character in height.

That seems unnecessary - why should 2 more pixels in height necessitate such
a gross resizing? I guess the answer is that frames and windows must be an
integral number of characters in height. But it still seems odd.

If I set `resize-mini-windows' = nil, the boxed character is shown
completely, including both top and bottom box borders, so I don't think the
resizing is because "the contents require more space" (from the doc).
Something seems wrong with the computation of the needed height. Unless,
that is, an additional space is supposed to always be present above and
below the displayed characters.

The Elisp manual also says, to introduce the idea of resizing, "The
minibuffer's window is normally a single line..." It should say "The
minibuffer's height is that of a single line", because as it stands now it
gives the impression that additional lines are added during resizing. In
what I see, there is still only a single minibuffer line (single line of
text), but the minibuffer height is increased.

FYI, this is the face I put on a character, to provoke the jump in height:

(defface foo
    '((((type x w32 mac graphic) (class color))
       (:box (:line-width 1 :color "Red") :foreground "Red" :background
"Cyan"))
      (t (:inverse-video t)))
  "..." :group 'faces)

If I use a standalone minibuffer frame, I see no change in height, BTW.
Perhaps that is because there is sufficient height already; I'm not sure.

             reply	other threads:[~2007-01-08 23:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-08 23:24 Drew Adams [this message]
2007-01-09  4:08 ` resize-mini-windows Richard Stallman
2007-03-13 17:50 ` resize-mini-windows Drew Adams
2007-03-13 20:22   ` resize-mini-windows Miles Bader
2007-03-14  2:44     ` resize-mini-windows Drew Adams
2007-03-14  4:50       ` resize-mini-windows Miles Bader
2007-03-14  7:28         ` resize-mini-windows Drew Adams

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=BDEIJAFNGDOAGCJIPKPBIENMCBAA.drew.adams@oracle.com \
    --to=drew.adams@oracle.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).