From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Richard M. Stallman" Newsgroups: gmane.emacs.devel,gmane.emacs.help Subject: Re: Q on minibuffer-message Date: Sun, 22 Jan 2006 12:44:57 -0500 Message-ID: References: <43D16944.1020407@student.lu.se> Reply-To: rms@gnu.org NNTP-Posting-Host: main.gmane.org Content-Type: text/plain; charset=ISO-8859-15 X-Trace: sea.gmane.org 1137961936 4463 80.91.229.2 (22 Jan 2006 20:32:16 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 22 Jan 2006 20:32:16 +0000 (UTC) Cc: help-gnu-emacs@gnu.org, drew.adams@oracle.com, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jan 22 21:32:14 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 1F0lse-00024U-Ko for ged-emacs-devel@m.gmane.org; Sun, 22 Jan 2006 21:32:08 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1F0lvF-0004MZ-Vq for ged-emacs-devel@m.gmane.org; Sun, 22 Jan 2006 15:34:50 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1F0jMt-0002kE-7z for emacs-devel@gnu.org; Sun, 22 Jan 2006 12:51:11 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1F0jMq-0002j2-ED for emacs-devel@gnu.org; Sun, 22 Jan 2006 12:51:08 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1F0jMo-0002io-EC; Sun, 22 Jan 2006 12:51:06 -0500 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1F0jRP-0002AH-K5; Sun, 22 Jan 2006 12:55:51 -0500 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.34) id 1F0jGr-00069s-Ld; Sun, 22 Jan 2006 12:44:57 -0500 Original-To: Lennart Borgman In-reply-to: <43D16944.1020407@student.lu.se> (message from Lennart Borgman on Fri, 20 Jan 2006 23:50:44 +0100) 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:49408 gmane.emacs.help:32777 Archived-At: > I have a command `foo' that calls `minibuffer-message' at various points. > > I want to call this function from another command, `bar', but I don't want > the `minibuffer-message' display to wait for two seconds - I even don't care > if it is displayed at all in this case. It is not useful to display a minibuffer message and not wait to give the user a chance to see it. The operation must normally wait. Perhaps what you mean is that when foo is used from bar, you see no reason for foo's messages to appear at all. In that case, what I suggest is that you set up foo with an optional argument that is provided as t when it is called interactively. And foo should only display its messages when that argument is t.