From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Drew Adams" Newsgroups: gmane.emacs.devel,gmane.emacs.help Subject: RE: Q on minibuffer-message Date: Mon, 23 Jan 2006 09:19:29 -0800 Message-ID: References: <87irsbo7et.fsf@gmail.com> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1138047820 16994 80.91.229.2 (23 Jan 2006 20:23:40 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 23 Jan 2006 20:23:40 +0000 (UTC) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jan 23 21:23:38 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1F18DL-0004ZP-UN for ged-emacs-devel@m.gmane.org; Mon, 23 Jan 2006 21:23:02 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1F17Af-0000U2-5e for ged-emacs-devel@m.gmane.org; Mon, 23 Jan 2006 14:16:09 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1F15Oh-0007Lt-BS for emacs-devel@gnu.org; Mon, 23 Jan 2006 12:22:32 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1F15Oa-0007JV-Gk for emacs-devel@gnu.org; Mon, 23 Jan 2006 12:22:29 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1F15OY-0007J2-V3; Mon, 23 Jan 2006 12:22:23 -0500 Original-Received: from [141.146.126.228] (helo=agminet01.oracle.com) by monty-python.gnu.org with esmtp (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA:24) (Exim 4.34) id 1F15TJ-0001OZ-Aw; Mon, 23 Jan 2006 12:27:18 -0500 Original-Received: from rgmsgw301.us.oracle.com (rgmsgw301.us.oracle.com [138.1.186.50]) by agminet01.oracle.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id k0NHJUI7024798; Mon, 23 Jan 2006 11:19:30 -0600 Original-Received: from rgmsgw301.us.oracle.com (localhost [127.0.0.1]) by rgmsgw301.us.oracle.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id k0NHJUfR014585; Mon, 23 Jan 2006 10:19:30 -0700 Original-Received: from dradamslap (dradams-lap.us.oracle.com [130.35.177.126]) by rgmsgw301.us.oracle.com (Switch-3.1.7/Switch-3.1.7) with SMTP id k0NHJT8I014577 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Mon, 23 Jan 2006 10:19:29 -0700 Original-To: , "Emacs-Devel" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: <87irsbo7et.fsf@gmail.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506 Importance: Normal X-Brightmail-Tracker: AAAAAQAAAAI= X-Whitelist: TRUE 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:49449 gmane.emacs.help:32798 Archived-At: Drew> I could change the definition of command `foo', to pass it a flag to not call `minibuffer-message' (or to call it only when the command is called interactively), but I'd rather not have to resort to that. Eli> This doesn't explain why you wanted to avoid such a solution. In fact, I have always planned anyway to modify `foo' in this way, because my library needs to work also with Emacs 20, which has no `minibuffer-message-timeout'. When I said that I wished to avoid such modification, what I meant was that one should be able to avoid it. Ian> But why? The argument can be optional, meaning if it's not given it will default to nil. So there's no need to modify call sites in programs. The concern was not needing to modify functions that call `foo'. The concern was needing to modify `foo', the function that calls `minibuffer-message'. The point is that it would be useful to be able to inhibit the action of `minibuffer-message' from _without_, just as you can turn off logging of messages in buffer *Messages* from without. Imagine a scenario where you have no control over the definition of `foo'. You simply want to use it, but not hear its `minibuffer-message' noise. Binding `minibuffer-message-timeout' to 0 (or nil, or t, or whatever) should let you do that. That's all.