From: "Drew Adams" <drew.adams@oracle.com>
To: <herring@lanl.gov>
Cc: 'Deniz Dogan' <deniz.a.m.dogan@gmail.com>, emacs-devel@gnu.org
Subject: RE: Rename `mini-' options
Date: Fri, 15 May 2009 19:11:28 -0700 [thread overview]
Message-ID: <002f01c9d5cb$9fd36b00$0200a8c0@us.oracle.com> (raw)
In-Reply-To: <26694.128.165.0.81.1242438439.squirrel@webmail.lanl.gov>
> >> This is the first time I encounter something called "mini-windows",
> >> but it seems to me, after having read the documentation for the
> >> variable, that the minibuffer is an instance of them? Are there any
> >> other mini-windows or is this just very poorly documented?
> >
> > Just poorly named and poorly documented. What is meant is
> > the (active) minibuffer window.
> >
> > There can be more than one minibuffer window, but only one
> > is active at any time.
>
> The mini-window is the window that holds the minibuffer,
Nice try ;-). But you're simply making that up.
> but also the echo area. Try evaluating this with `eval-region':
> (let (resize-mini-windows)
> (message (make-string 100 100))
> (sit-for 1))
Yes, of course. The minibuffer and the echo area share the same screen real
estate. But it's not a window - "window" means something specific in Emacs.
Is there a need for some new name to identify that screen area? Maybe, maybe
not. In any case, "mini-window" is not, today, such an identifier.
There ain't no such definition. Try `M-x apropos mini-'. Search the Emacs manual
for `mini-'. Search the Elisp manual. You will find only these poorly named
variables. Search the manuals and doc strings for "mini window" - nada.
If we want to discuss whether there should be a name for this common area, we
can. If we finally decide that there should be, then we can discuss what that
name should be. It certainly should not have "window" in it, as that is
misleading. There is no window that corresponds to the echo area: its messages
are not displayed in a window.
Most importantly, to come back to the point: Users will not easily find these
particular options - whether they look for `minibuffer' or `echo-area'.
next prev parent reply other threads:[~2009-05-16 2:11 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 [this message]
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
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='002f01c9d5cb$9fd36b00$0200a8c0@us.oracle.com' \
--to=drew.adams@oracle.com \
--cc=deniz.a.m.dogan@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=herring@lanl.gov \
/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.