From: Miles Bader <miles@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: Rename `mini-' options
Date: Sun, 17 May 2009 10:59:17 +0900 [thread overview]
Message-ID: <874ovk7ami.fsf@catnip.gol.com> (raw)
In-Reply-To: 002601c9d65b$937ef9b0$0200a8c0@us.oracle.com
"Drew Adams" <drew.adams@oracle.com> writes:
> But that is not the case here. The doc string talks only about resizing
> `mini-windows', without ever giving a clue what a `mini-window' is. Might as
> well talk about resizing `thronbolts'.
Sorry, that's not true. "mini-window" is hardly an inspired term, but
despite being kind of ad-hoc, it's not a random word, and that makes a
big difference. When I first saw that variable, I instantly realized
what it probably meant.
[exactly why, I dunno -- maybe it's because "mini" ~= "minibuffer", and
hey, "-window", so it's that window... maybe it's just because
"mini-window" suggests a very small window, let's see... what on my
display is a very small window ... aha! -- anyway regardless of the
thought process, it worked on me.]
Now, maybe you were completely confused by those variable names, I
dunno, but I agree that if we can find a better terminology that makes
everybody happy, great!
>> Of course, it's not always to come up with a good term, but
>> I'm not sure what other term would be better. The terms you
>> suggested are pithy, but seem inaccurate.
>
> how is `minibuffer-echo-area-resize' inaccurate?
That's not the term you suggested; you said, in your original message:
> It would have been sufficient, if the name length were so important, to use
> `minibuffer-resize' or `minibuf-auto-resize'. Similarly,
> `minibuffer-max-height'. And `minibuffer' should probably come first in the
> name: `minibuffer-resize', not `resize-minibuffer'.
Such terms are inaccurate because they just say "minibuffer", which is a
something different -- a _minibuffer_ is the actual editable thingie
that is involved in user input.
That's why "minibuffer-window" is better: it doesn't refer to
minibuffers per-se, but rather to the window used to display them, which
is something different.
-Miles
--
"She looks like the wax version of herself."
[Comment under a Paris Hilton fashion pic]
next prev parent reply other threads:[~2009-05-17 1:59 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
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 [this message]
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=874ovk7ami.fsf@catnip.gol.com \
--to=miles@gnu.org \
--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.