From: Artur Malabarba <bruce.connor.am@gmail.com>
To: Rasmus <rasmus@gmx.us>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Async package.el
Date: Thu, 9 Apr 2015 15:53:14 +0100 [thread overview]
Message-ID: <CAAdUY-J6QhuE9_eGiLvFjXdN8A_jvGZEarOOOh0hidzOh9FaBA@mail.gmail.com> (raw)
In-Reply-To: <CAAdUY-JxFyNgy_xbC=ww53fRMqgRx4=fLf0W2rNDcRtFBMc_vw@mail.gmail.com>
There are some C-level functions that send messages without using
`message', but these are very few.
There's also an emacs package dedicated to muting messages, I think
it's called `shut-up' (or something like that).
2015-04-09 15:50 GMT+01:00 Artur Malabarba <bruce.connor.am@gmail.com>:
>>> I need to find a
>>> way of telling #'message not to talk when called from an async
>>> task -- or more generally, if called from anything except the main UI
>>> thread. Any ideas?
>>
>> Is something like this too hackish?
>>
>> (cl-letf (((symbol-function 'message) 'ignore))
>> whatever)
>>
>
> This is generally what I do too. IIRC, the only drawback is that this
> uses unwind-protect, which is not triggered by the max-lisp-eval-depth
> error. So if you hit that error, message's function definition won't
> be restored.
> You can either just live with that, or you can wrap the code inside
> the `cl-letf' in a `condition-case' statement and to catch that error.
next prev parent reply other threads:[~2015-04-09 14:53 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-06 10:46 Async package.el Artur Malabarba
2015-04-06 13:53 ` Dmitry Gutov
2015-04-06 14:32 ` Artur Malabarba
2015-04-07 1:19 ` Dmitry Gutov
2015-04-07 21:46 ` Stefan Monnier
2015-04-08 1:49 ` Dmitry Gutov
2015-04-08 13:32 ` Stefan Monnier
2015-04-09 1:49 ` Dmitry Gutov
2015-04-09 14:06 ` raman
2015-04-09 14:22 ` Rasmus
2015-04-09 14:50 ` Artur Malabarba
2015-04-09 14:53 ` Artur Malabarba [this message]
2015-04-09 15:19 ` async message Ivan Shmakov
2015-04-10 14:58 ` raman
2015-04-10 1:32 ` Async package.el raman
2015-04-09 18:18 ` Stefan Monnier
2015-04-10 15:00 ` raman
2015-04-12 0:46 ` Artur Malabarba
2015-04-12 3:53 ` Stefan Monnier
2015-04-07 23:26 ` Artur Malabarba
2015-04-08 2:19 ` Dmitry Gutov
2015-04-08 9:43 ` Artur Malabarba
2015-04-08 16:02 ` Dmitry Gutov
2015-04-08 18:39 ` Artur Malabarba
2015-04-09 2:10 ` Dmitry Gutov
2015-04-09 10:14 ` Artur Malabarba
2015-04-09 12:34 ` Dmitry Gutov
2015-04-12 1:38 ` Artur Malabarba
2015-04-07 5:31 ` Daiki Ueno
2015-04-07 9:13 ` Dmitry Gutov
2015-04-07 9:59 ` Artur Malabarba
2015-04-07 11:22 ` Robert Pluim
2015-04-07 12:33 ` Artur Malabarba
2015-04-07 14:29 ` Robert Pluim
2015-04-08 2:21 ` Artur Malabarba
2015-04-07 21:50 ` Stefan Monnier
2015-04-08 5:27 ` Daiki Ueno
2015-04-09 8:38 ` Achim Gratz
2015-04-09 13:09 ` Stefan Monnier
2015-04-07 18:06 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAAdUY-J6QhuE9_eGiLvFjXdN8A_jvGZEarOOOh0hidzOh9FaBA@mail.gmail.com \
--to=bruce.connor.am@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=rasmus@gmx.us \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.