From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Thierry Volpiatto <thierry.volpiatto@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Why timers are now catching errors
Date: Sun, 13 Jan 2013 10:34:22 -0500 [thread overview]
Message-ID: <jwvr4lpt7z5.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <871udpi151.fsf@gmail.com> (Thierry Volpiatto's message of "Sun, 13 Jan 2013 15:54:50 +0100")
>>> This change will break many commands using timers.
> You should read "annoy", it break nothing, just send repeatedly an
> annoying message. (See eldoc-eval.el)
Ah, so the problem is the `message' call?
If so, that's easy to fix: wrap the timer's code inside its own
condition-case to catch the error before timer.el does.
> But maybe you are intoducing (temporarily) such code to improve some
> timer functions running in emacs ?
It's definitely not temporary, no. Silently dropping such errors makes
tracking down bugs much harder, so it's here to stay.
Stefan
next prev parent reply other threads:[~2013-01-13 15:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-13 13:24 Why timers are now catching errors Thierry Volpiatto
2013-01-13 14:29 ` Stefan Monnier
2013-01-13 14:54 ` Thierry Volpiatto
2013-01-13 15:34 ` Stefan Monnier [this message]
2013-01-13 15:51 ` Thierry Volpiatto
2013-01-13 15:55 ` Thierry Volpiatto
2013-01-13 17:30 ` Thierry Volpiatto
2013-01-13 18:13 ` Eli Zaretskii
2013-01-13 18:18 ` Eli Zaretskii
2013-01-13 18:38 ` Thierry Volpiatto
2013-01-13 18:52 ` Thierry Volpiatto
2013-01-13 19:02 ` Eli Zaretskii
2013-01-13 19:07 ` Thierry Volpiatto
2013-01-13 20:05 ` Eli Zaretskii
2013-01-13 20:37 ` Eli Zaretskii
2013-01-13 20:22 ` Eli Zaretskii
2013-01-13 20:31 ` Thierry Volpiatto
2013-01-13 22:55 ` Stefan Monnier
2013-01-13 23:03 ` chad
2013-01-14 1:28 ` Stefan Monnier
2013-01-13 22:50 ` 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=jwvr4lpt7z5.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=thierry.volpiatto@gmail.com \
/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.