I have a couple of background processes that I regularly run, such as mu4e and jabber-mode.
These, and other, processes provide updates to the minibuffer. Unfortunately, they do so when I'm already interacting with the minibuffer.
How can I prevent this happening, or at least dismiss the message so I can continue interacting with the minibuffer?
process-filterand send the string of process output directly to the*Messages*buffer withinsertand I let-bindinhibit-read-onlyand create the buffer in the proper mode if doesn't already exist. See this related thread -- Send process output to Messages buffer, but bypass the echo area: emacs.stackexchange.com/a/6003/2287 If one of your offending functions mentioned in the question have amessagebeing created, you may wish to consider commenting that out or modifying it to a concept similar to the link in this comment -- i.e., just insert. – lawlist May 3 '16 at 13:57inhibit-message: superuser.com/a/927832/206164 The doc-string states: "Non-nil means calls to ‘message’ are not displayed. They are still logged to the*Messages*buffer." – lawlist May 3 '16 at 14:10minibuffer-messageto write to the active minibuffer? – Drew May 3 '16 at 14:28