From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Drew Adams" Newsgroups: gmane.emacs.devel Subject: RE: minibuffer-message binds inhibit-quit Date: Tue, 24 Jun 2008 15:26:14 -0700 Message-ID: <002d01c8d649$50b8e3b0$0200a8c0@us.oracle.com> References: <001a01c8d63c$273e5f40$0200a8c0@us.oracle.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1214346442 14010 80.91.229.12 (24 Jun 2008 22:27:22 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 24 Jun 2008 22:27:22 +0000 (UTC) Cc: emacs-devel@gnu.org To: "'Eli Zaretskii'" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jun 25 00:28:07 2008 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 1KBGze-0001jk-Jv for ged-emacs-devel@m.gmane.org; Wed, 25 Jun 2008 00:28:07 +0200 Original-Received: from localhost ([127.0.0.1]:50152 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KBGyo-0002X6-HL for ged-emacs-devel@m.gmane.org; Tue, 24 Jun 2008 18:27:14 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KBGyi-0002Vg-1c for emacs-devel@gnu.org; Tue, 24 Jun 2008 18:27:08 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KBGye-0002Si-VY for emacs-devel@gnu.org; Tue, 24 Jun 2008 18:27:07 -0400 Original-Received: from [199.232.76.173] (port=53508 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KBGye-0002SS-FF for emacs-devel@gnu.org; Tue, 24 Jun 2008 18:27:04 -0400 Original-Received: from rgminet01.oracle.com ([148.87.113.118]:32846) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1KBGyZ-0005i5-SA; Tue, 24 Jun 2008 18:27:00 -0400 Original-Received: from agmgw1.us.oracle.com (agmgw1.us.oracle.com [152.68.180.212]) by rgminet01.oracle.com (Switch-3.2.4/Switch-3.1.6) with ESMTP id m5OMQuPs023957; Tue, 24 Jun 2008 16:26:56 -0600 Original-Received: from acsmt350.oracle.com (acsmt350.oracle.com [141.146.40.150]) by agmgw1.us.oracle.com (Switch-3.2.0/Switch-3.2.0) with ESMTP id m5OMQtwk026257; Tue, 24 Jun 2008 16:26:56 -0600 Original-Received: from inet-141-146-46-1.oracle.com by acsmt350.oracle.com with ESMTP id 3698659141214346369; Tue, 24 Jun 2008 15:26:09 -0700 Original-Received: from dradamslap1 (/141.144.81.15) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Tue, 24 Jun 2008 15:26:09 -0700 X-Mailer: Microsoft Office Outlook 11 In-Reply-To: Thread-Index: AcjWQV4ZMOj++5dMRimjAUV5fzS+EgAACh6w X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 X-Brightmail-Tracker: AAAAAQAAAAI= X-Brightmail-Tracker: AAAAAQAAAAI= X-Whitelist: TRUE X-Whitelist: TRUE X-detected-kernel: by monty-python.gnu.org: Linux 2.4-2.6 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:99873 Archived-At: > Are you sure you are not confusing minibuffer with the echo area? The > minibuffer and `minibuffer-message' are not normally used for messages > during minibuffer input; that's what the echo area is for. No, I don't believe so. AFAIK, `minibuffer-message' has always displayed a message in the minibuffer, not the echo area. You see your input there at the same time. `message', on the other hand, displays in the echo area. The echo-area obscures the minibuffer; the message replaces the minibuffer content (temporarily). AFAIK, `minibuffer-message' is intended to be used during minibuffer input. "This function displays STRING temporarily at the end of the minibuffer text, for two seconds, or until the next input event arrives, whichever comes first." "The text is displayed for a period controlled by `minibuffer-message-timeout', or until the next input event arrives, whichever comes first." [BTW, note the discrepancy between the Elisp manual entry and the doc string, wrt the timeout period.] FWIW, I tend to use this, which chooses the display function depending on whether the minibuffer is active: (defun icicle-msg-maybe-in-minibuffer (format-string &rest args) "Display FORMAT-STRING as a message. If called with the minibuffer inactive, this is done using `message'. Otherwise, it is done using `minibuffer-message'." (if (active-minibuffer-window) (save-selected-window (select-window (minibuffer-window)) (minibuffer-message (apply #'format (concat " [" format-string "]") args))) (apply #'message format-string args)))