From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: Drew Adams <drew.adams@oracle.com>, emacs-devel@gnu.org
Subject: Re: Rename `mini-' options
Date: Sat, 16 May 2009 15:43:37 +0900 [thread overview]
Message-ID: <873ab5fsyu.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <f7ccd24b0905152009m655042e9w9f782316c6126599@mail.gmail.com>
Juanma Barranquero writes:
> 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.
So does max-mini-window-height. And as your own words and the
existing documentation which you quote demonstrate:
jb> What is the difference between the frame's minibuffer window, and the
jb> screen real state used by the minibuffer?
doc> The variable `max-mini-window-height', which specifies the maximum
doc> height for resizing minibuffer windows, also applies to the echo area
doc> (which is really a special use of the minibuffer window. *Note
doc> Minibuffer Misc::.).
the name of the window in question is "minibuffer window".
Drew is right. It is inconsistent with existing practice, and
confuses something that is already rife with possibilities for
confusion. And "mini-window" strongly suggests a new class of "small
window" objects, which doesn't exist. There is precedent in the
3d-party resize-minibuffer mode, where the following names already
exist:
* resize-minibuffer-frame-max-height - Maximum size the minibuffer
frame is allowed to become.
* resize-minibuffer-idle-height - When minibuffer is idle, crop its
window to this height.
* resize-minibuffer-window-max-height - Maximum size the minibuffer
window is allowed to become.
Please fix the "mini-" names.
next prev parent reply other threads:[~2009-05-16 6:43 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
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 [this message]
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=873ab5fsyu.fsf@uwakimon.sk.tsukuba.ac.jp \
--to=stephen@xemacs.org \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.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 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.