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: Fri, 16 Jan 2009 15:52:18 -0500 Message-ID: References: <87y6xedc47.fsf@jurta.org> <87ocyat2y5.fsf@cyd.mit.edu> <000401c9765c$e7d22eb0$0200a8c0@us.oracle.com> <87tz818udp.fsf@jurta.org> <002d01c97696$93c6a190$c2b22382@us.oracle.com> <004f01c976ab$8611f9e0$c2b22382@us.oracle.com> <006801c9780e$1a0db130$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 1232139155 13684 80.91.229.12 (16 Jan 2009 20:52:35 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 16 Jan 2009 20:52:35 +0000 (UTC) Cc: 'Juri Linkov' , 'Chong Yidong' , 'Geoff Gole' , emacs-devel@gnu.org To: "Drew Adams" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jan 16 21:53:46 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 1LNvhJ-00015W-BE for ged-emacs-devel@m.gmane.org; Fri, 16 Jan 2009 21:53:45 +0100 Original-Received: from localhost ([127.0.0.1]:49158 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LNvg2-0002Vk-4I for ged-emacs-devel@m.gmane.org; Fri, 16 Jan 2009 15:52:26 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LNvfx-0002SZ-Bl for emacs-devel@gnu.org; Fri, 16 Jan 2009 15:52:21 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LNvfv-0002Pl-Vr for emacs-devel@gnu.org; Fri, 16 Jan 2009 15:52:21 -0500 Original-Received: from [199.232.76.173] (port=59403 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LNvfv-0002Pf-OS for emacs-devel@gnu.org; Fri, 16 Jan 2009 15:52:19 -0500 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.182]:16840) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LNvfv-0003s4-Dv for emacs-devel@gnu.org; Fri, 16 Jan 2009 15:52:19 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AkQFAAOCcElMCpxj/2dsb2JhbACBbMt/hXKBfw X-IronPort-AV: E=Sophos;i="4.37,278,1231131600"; d="scan'208";a="32429068" Original-Received: from 76-10-156-99.dsl.teksavvy.com (HELO pastel.home) ([76.10.156.99]) by ironport2-out.teksavvy.com with ESMTP; 16 Jan 2009 15:52:18 -0500 Original-Received: by pastel.home (Postfix, from userid 20848) id 6E34B7F97; Fri, 16 Jan 2009 15:52:18 -0500 (EST) In-Reply-To: <006801c9780e$1a0db130$0200a8c0@us.oracle.com> (Drew Adams's message of "Fri, 16 Jan 2009 11:10:30 -0800") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. 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:107914 Archived-At: >> Say you have a M-x minibuffer open but you've switched to some other >> buffer, say a shell buffer and you're using completion and the >> completion code needs to say "Sole completion": your suggestion would >> cause a " [Sole completion]" message to be added at the end of the M-x >> minibuffer (i.e. an unrelated minibuffer), rather than replacing >> it altogether. > No, it would not, because I would not use the DWIM function > (`msg-maybe-in-minibuffer') to display such a message. I would not, > because the shell completion code in question is not using the > minibuffer, and it is unlikely that it would ever be called from > the minibuffer. Huh? The shell completion is used in M-! Also I have some work-in-progress patches to replace some of the shell and lisp-symbol completion code (and sym-comp.el) to use minibuffer-complete. There very much is a need for this completion code to magically decide when to use message and when to use minibuffer-message, and until now the best test I've found is minibufferp, not active-minibuffer-window. Stefan