unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Oleh Krehel <ohwoeowho@gmail.com>
To: emacs-devel@gnu.org
Subject: Is there a way to inhibit message3 from Elisp?
Date: Tue, 21 Apr 2015 15:37:39 +0200	[thread overview]
Message-ID: <87618psiu4.fsf@gmail.com> (raw)

Hi all,

I think this option would be quite useful in general, if it's not yet
implemented, which I'm pretty sure it's not.

My particular use-case is that I'm doing completion in the minibuffer
with ivy.el, calling `shell-command-to-string' in the `post-command-hook'.
And when I enable `while-no-input' in my function, my minibuffer
contents get rudely interrupted by `call_process_cleanup' saying:

> "Waiting for process to die...done"

I'm sure that this message is needed and appericated, but I'd like to
have an option to suppress it. I think a variable like `inhibit-message'
that I could let-bind would be a good solution to my problem.

I've seen this question brought up a few times on the stack exchange
sites, what people tend to do is to `flet'-override the `message'
function.  It doesn't apply in this case, but the solution to this
problem would solve the other ones too.

Oleh



             reply	other threads:[~2015-04-21 13:37 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-21 13:37 Oleh Krehel [this message]
2015-04-21 17:17 ` Is there a way to inhibit message3 from Elisp? Stefan Monnier
2015-04-21 18:50   ` Oleh Krehel
2015-04-21 23:25     ` Artur Malabarba
2015-04-22  6:00       ` Oleh Krehel
2015-04-22 10:53     ` Eli Zaretskii
2015-04-22 11:55       ` Oleh Krehel
2015-04-22 12:24         ` Eli Zaretskii
2015-04-22 12:50           ` Oleh Krehel
2015-04-22 13:01             ` Eli Zaretskii
2015-04-22 13:51           ` Stefan Monnier
2015-04-22 13:48             ` Oleh Krehel
2015-04-22 17:39             ` Artur Malabarba
2015-04-22 20:20               ` Stefan Monnier
2015-04-22 12:42         ` Artur Malabarba
2015-04-22 17:22         ` Artur Malabarba
2015-04-22 17:20           ` Oleh Krehel
2015-04-22 13:53     ` Stefan Monnier

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=87618psiu4.fsf@gmail.com \
    --to=ohwoeowho@gmail.com \
    --cc=emacs-devel@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).