From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: minibuffer-message binds inhibit-quit Date: Wed, 25 Jun 2008 00:28:41 +0300 Message-ID: References: <001a01c8d63c$273e5f40$0200a8c0@us.oracle.com> Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org X-Trace: ger.gmane.org 1214342942 2811 80.91.229.12 (24 Jun 2008 21:29:02 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 24 Jun 2008 21:29:02 +0000 (UTC) Cc: emacs-devel@gnu.org To: Drew Adams Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jun 24 23:29:46 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 1KBG58-0001uW-Eq for ged-emacs-devel@m.gmane.org; Tue, 24 Jun 2008 23:29:42 +0200 Original-Received: from localhost ([127.0.0.1]:33774 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KBG4J-00047p-1N for ged-emacs-devel@m.gmane.org; Tue, 24 Jun 2008 17:28:51 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KBG4F-00047k-1l for emacs-devel@gnu.org; Tue, 24 Jun 2008 17:28:47 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KBG4B-00047P-Tq for emacs-devel@gnu.org; Tue, 24 Jun 2008 17:28:45 -0400 Original-Received: from [199.232.76.173] (port=60877 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KBG4B-00047M-N2 for emacs-devel@gnu.org; Tue, 24 Jun 2008 17:28:43 -0400 Original-Received: from mtaout1.012.net.il ([84.95.2.1]:9244) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KBG4B-0005J2-6u for emacs-devel@gnu.org; Tue, 24 Jun 2008 17:28:43 -0400 Original-Received: from HOME-C4E4A596F7 ([80.230.31.196]) by i-mtaout1.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0K2Z00C7JLP7O6M0@i-mtaout1.012.net.il> for emacs-devel@gnu.org; Wed, 25 Jun 2008 00:43:55 +0300 (IDT) In-reply-to: <001a01c8d63c$273e5f40$0200a8c0@us.oracle.com> X-012-Sender: halo1@inter.net.il X-detected-kernel: by monty-python.gnu.org: Solaris 9.1 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:99869 Archived-At: > From: "Drew Adams" > Date: Tue, 24 Jun 2008 13:52:01 -0700 > > This let binding was recently added to `minibuffer-message': > > ;; A quit during sit-for normally only interrupts the sit-for, > ;; but since minibuffer-message is used at the end of a command, > ;; at a time when the command has virtually finished already, a C-g > ;; should really cause an abort-recursive-edit instead (i.e. as if > ;; the C-g had been typed at top-level). Binding inhibit-quit here > ;; is an attempt to get that behavior. > (inhibit-quit t) > > I don't know about the effects of the binding (can't check until I get a more > recent Windows build) - perhaps this change is appropriate. But if it requires > the assumption stated in the comment, then it is not appropriate. > > The assumption is invalid - it is by no means necessarily true that > "minibuffer-message is used at the end of a command, at a time when the command > has virtually finished already". > > `minibuffer-message' should be for messages during minibuffer input - that's > all. Nothing should be assumed about when the command that calls it might be > ended or is "virtually finished". 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.