unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Richard M. Stallman" <rms@gnu.org>
Cc: help-gnu-emacs@gnu.org, drew.adams@oracle.com, emacs-devel@gnu.org
Subject: Re: Q on minibuffer-message
Date: Sun, 22 Jan 2006 12:44:57 -0500	[thread overview]
Message-ID: <E1F0jGr-00069s-Ld@fencepost.gnu.org> (raw)
In-Reply-To: <43D16944.1020407@student.lu.se> (message from Lennart Borgman on Fri, 20 Jan 2006 23:50:44 +0100)

    > 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.

  parent reply	other threads:[~2006-01-22 17:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <MEEKKIABFKKDFJMPIOEBIEJMCOAA.drew.adams@oracle.com>
2006-01-20 22:50 ` Q on minibuffer-message Lennart Borgman
2006-01-20 23:08   ` Drew Adams
2006-01-22 17:44   ` Richard M. Stallman [this message]
2006-01-22 18:54     ` Drew Adams
2006-01-23  4:42       ` Eli Zaretskii
2006-01-24 16:46       ` Richard M. Stallman
     [not found] <87irsbo7et.fsf@gmail.com>
2006-01-23 17:19 ` Drew Adams
2006-01-23 23:23   ` Eli Zaretskii
2006-01-24  0:10     ` Drew Adams
2006-01-24  4:28       ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1F0jGr-00069s-Ld@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=help-gnu-emacs@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).