From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Stephen J. Turnbull" Newsgroups: gmane.emacs.devel Subject: Re: Rename `mini-' options Date: Sat, 16 May 2009 15:43:37 +0900 Message-ID: <873ab5fsyu.fsf@uwakimon.sk.tsukuba.ac.jp> References: <26694.128.165.0.81.1242438439.squirrel@webmail.lanl.gov> <002f01c9d5cb$9fd36b00$0200a8c0@us.oracle.com> <003001c9d5ce$a044ea20$0200a8c0@us.oracle.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1242455875 5599 80.91.229.12 (16 May 2009 06:37:55 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 16 May 2009 06:37:55 +0000 (UTC) Cc: Drew Adams , emacs-devel@gnu.org To: Juanma Barranquero Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat May 16 08:37:42 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1M5DWe-0008O5-RE for ged-emacs-devel@m.gmane.org; Sat, 16 May 2009 08:37:41 +0200 Original-Received: from localhost ([127.0.0.1]:38434 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M5DWe-0000WM-Ab for ged-emacs-devel@m.gmane.org; Sat, 16 May 2009 02:37:40 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1M5DWY-0000V4-Vl for emacs-devel@gnu.org; Sat, 16 May 2009 02:37:35 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1M5DWT-0000Rw-4n for emacs-devel@gnu.org; Sat, 16 May 2009 02:37:33 -0400 Original-Received: from [199.232.76.173] (port=40812 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M5DWS-0000Rq-Vb for emacs-devel@gnu.org; Sat, 16 May 2009 02:37:29 -0400 Original-Received: from mtps02.sk.tsukuba.ac.jp ([130.158.97.224]:37452) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1M5DWS-0002hq-FL for emacs-devel@gnu.org; Sat, 16 May 2009 02:37:28 -0400 Original-Received: from uwakimon.sk.tsukuba.ac.jp (uwakimon.sk.tsukuba.ac.jp [130.158.99.156]) by mtps02.sk.tsukuba.ac.jp (Postfix) with ESMTP id 6D93D820F; Sat, 16 May 2009 15:37:26 +0900 (JST) Original-Received: by uwakimon.sk.tsukuba.ac.jp (Postfix, from userid 1000) id 21B231A4583; Sat, 16 May 2009 15:43:37 +0900 (JST) In-Reply-To: X-Mailer: VM 8.0.12-devo-585 under 21.5 (beta28) "fuki" 83e35df20028+ XEmacs Lucid (x86_64-unknown-linux) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:110916 Archived-At: 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.