Re: Rename `mini-' options

["Stephen J. Turnbull" <stephen@xemacs.org>]

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.