unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Miles Bader <miles@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: Rename `mini-' options
Date: Sat, 16 May 2009 16:13:03 +0900	[thread overview]
Message-ID: <87r5yp7c74.fsf@catnip.gol.com> (raw)
In-Reply-To: 873ab5fsyu.fsf@uwakimon.sk.tsukuba.ac.jp

"Stephen J. Turnbull" <stephen@xemacs.org> writes:
> the name of the window in question is "minibuffer window".

Er, except that it's not.

For better or worse, Emacs traditionally distinguishes "the minibuffer"
from "the echo area", and resize-mini-windows applies to both.  So a
name which captures this subtlety is arguably better than one which lies
a bit for the sake of convenient document searching.

> Drew is right.  It is inconsistent with existing practice, and
> confuses something that is already rife with possibilities for
> confusion.

The variable in question _is_ existing practice -- it was introduced
almost a decade ago, in Emacs 21.

> There is precedent in the 3d-party resize-minibuffer mode, where the
> following names already exist:

That (long obsolete) mode does something _different_ than
resize-mini-windows:  it only applies to the minibuffer.  Thus even if
referring to "minibuffer-window" makes sense for that mode, that doesn't
mean it makes sense for Emacs' builtin behavior.

[I suppose you could argue against the "echo area"/"minibuffer" split,
and say we should just refer to them both as "the minibuffer"
(or whatever), but that's a different argument (and certainly not
something that should happen right now, as it's a big change).]

-Miles

-- 
Education, n. That which discloses to the wise and disguises from the foolish
their lack of understanding.





  reply	other threads:[~2009-05-16  7:13 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 [this message]
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

  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=87r5yp7c74.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 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).