From: Juanma Barranquero <lekktu@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: emacs-devel@gnu.org, Deniz Dogan <deniz.a.m.dogan@gmail.com>
Subject: Re: Rename `mini-' options
Date: Sat, 16 May 2009 05:09:29 +0200 [thread overview]
Message-ID: <f7ccd24b0905152009m655042e9w9f782316c6126599@mail.gmail.com> (raw)
In-Reply-To: <003001c9d5ce$a044ea20$0200a8c0@us.oracle.com>
On Sat, May 16, 2009 at 04:32, Drew Adams <drew.adams@oracle.com> wrote:
> I did not say anything about the frame's minibuffer window. And yes, the
> minibuffer window is a window.
You said:
> The minibuffer and the echo area share the same screen real
> estate. But it's not a window - "window" means something specific in Emacs.
What is the difference between the frame's minibuffer window, and the
screen real state used by the minibuffer? (Unless you're trying to
imply that the "screen real state" is not a window, because a window
is an Emacs object, which would be handwaving IMO).
> 1. I said that the _echo area_ is not an Emacs window.
> Do you dispute that point?
No. I dispute that you said 1. Because Davis said
> The mini-window is the window that holds the minibuffer, but also
the echo area
and your answer was:
> Nice try ;-). But you're simply making that up.
As for the other points, the manual says:
The variable `max-mini-window-height', which specifies the maximum
height for resizing minibuffer windows, also applies to the echo area
(which is really a special use of the minibuffer window. *Note
Minibuffer Misc::.).
so, on one hand, it is not very difficult to find what is
max-mini-widow-height used for; and, on the other hand, changing it to
max-minibuffer-window-height would obscure the fact that the echo area
is also affected.
Juanma
next prev parent reply other threads:[~2009-05-16 3:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-16 1:47 Rename `mini-' options Davis Herring
2009-05-16 2:11 ` Drew Adams
2009-05-16 2:22 ` Juanma Barranquero
2009-05-16 2:32 ` Drew Adams
2009-05-16 3:09 ` Juanma Barranquero [this message]
2009-05-16 4:20 ` Drew Adams
2009-05-16 10:04 ` Eli Zaretskii
2009-05-16 19:20 ` Drew Adams
2009-05-16 19:47 ` Juanma Barranquero
2009-05-16 6:43 ` Stephen J. Turnbull
2009-05-16 7:13 ` Miles Bader
2009-05-16 8:24 ` Drew Adams
2009-05-16 9:21 ` Miles Bader
2009-05-16 19:21 ` Drew Adams
2009-05-17 1:59 ` Miles Bader
2009-05-16 9:18 ` Stephen J. Turnbull
2009-05-17 4:10 ` Stefan Monnier
[not found] <AcnVoAMCDVZ2cc3/RpaKtCkusD8ZRg==>
2009-05-15 20:59 ` Drew Adams
2009-05-16 0:12 ` Deniz Dogan
2009-05-16 0:21 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f7ccd24b0905152009m655042e9w9f782316c6126599@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=deniz.a.m.dogan@gmail.com \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.