From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Annoying paren match messages in minibuffer Date: Wed, 14 Jan 2009 16:52:56 -0500 Message-ID: References: <87y6xedc47.fsf@jurta.org> <87ocyat2y5.fsf@cyd.mit.edu> <000401c9765c$e7d22eb0$0200a8c0@us.oracle.com> <87tz818udp.fsf@jurta.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1231970066 5247 80.91.229.12 (14 Jan 2009 21:54:26 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 14 Jan 2009 21:54:26 +0000 (UTC) Cc: 'Chong Yidong' , 'Geoff Gole' , Drew Adams , emacs-devel@gnu.org To: Juri Linkov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jan 14 22:55:37 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 1LNDhd-0004UC-B2 for ged-emacs-devel@m.gmane.org; Wed, 14 Jan 2009 22:55:09 +0100 Original-Received: from localhost ([127.0.0.1]:53307 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LNDgN-0003Ux-0A for ged-emacs-devel@m.gmane.org; Wed, 14 Jan 2009 16:53:51 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LNDfc-0002b1-Fb for emacs-devel@gnu.org; Wed, 14 Jan 2009 16:53:04 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LNDfZ-0002XJ-Er for emacs-devel@gnu.org; Wed, 14 Jan 2009 16:53:03 -0500 Original-Received: from [199.232.76.173] (port=44204 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LNDfZ-0002Ww-8Y for emacs-devel@gnu.org; Wed, 14 Jan 2009 16:53:01 -0500 Original-Received: from pruche.dit.umontreal.ca ([132.204.246.22]:49189) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LNDfY-0002f4-UA for emacs-devel@gnu.org; Wed, 14 Jan 2009 16:53:01 -0500 Original-Received: from alfajor.home (vpn-132-204-232-55.acd.umontreal.ca [132.204.232.55]) by pruche.dit.umontreal.ca (8.14.1/8.14.1) with ESMTP id n0ELralM021815; Wed, 14 Jan 2009 16:53:36 -0500 Original-Received: by alfajor.home (Postfix, from userid 20848) id 4037B1C15B; Wed, 14 Jan 2009 16:52:56 -0500 (EST) In-Reply-To: <87tz818udp.fsf@jurta.org> (Juri Linkov's message of "Wed, 14 Jan 2009 23:12:18 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) X-NAI-Spam-Score: 0 X-NAI-Spam-Rules: 1 Rules triggered RV3189=0 X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 3) 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:107867 Archived-At: > As a general solution it would be better to change `message' > to take care about the minibuffer's case. I see 3 solutions: 1 - change `message' to use minibuffer-message when in the minibuffer. As pointed out, the delay can be problematic. 2 - change minibuffer-message to call `message' when not in minibuffer. This is easy to do and shouldn't suffer from those same problems but won't catch as many cases. 3 - introduce a new function that uses one or the other depending on `minibufferp'. This won't catch any case until we start changing code to use it. But it's the safest and easiest solution. The only hard part would be agreeing on its name. > I think `active-minibuffer-window' is not suitable for this. Indeed, we have `minibufferp' for that. Stefan