From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Daniel Mendler <mail@daniel-mendler.de>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Interrupting computations using signals
Date: Mon, 24 May 2021 12:34:25 -0400 [thread overview]
Message-ID: <jwva6okxf9h.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <3614444a-3b0b-a494-1b40-16e4823f0067@daniel-mendler.de> (Daniel Mendler's message of "Mon, 24 May 2021 17:12:20 +0200")
> (advice-add #'debug :around #'ignore)
Side note: it would be more honest to use `:override` here.
Stefan
prev parent reply other threads:[~2021-05-24 16:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 12:32 Interrupting computations using signals Daniel Mendler
2021-05-24 12:53 ` Eli Zaretskii
2021-05-24 14:08 ` Daniel Mendler
2021-05-24 14:37 ` Eli Zaretskii
2021-05-24 15:12 ` Daniel Mendler
2021-05-24 16:34 ` Stefan Monnier [this message]
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=jwva6okxf9h.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=mail@daniel-mendler.de \
/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).