From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 35400@debbugs.gnu.org
Subject: bug#35400: 27.0.50; Timers repeated after waking from suspend
Date: Tue, 23 Apr 2019 20:30:19 +0300 [thread overview]
Message-ID: <834l6o4ok4.fsf@gnu.org> (raw)
In-Reply-To: <jwvtveowtc1.fsf@iro.umontreal.ca> (message from Stefan Monnier on Tue, 23 Apr 2019 12:59:42 -0400)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Date: Tue, 23 Apr 2019 12:59:42 -0400
>
> now wait a minute and then
>
> kill -CONT <emacs-pid>
>
> and you should see something like:
>
> Run at: 12:49:40 [7 times]
>
> in the *Messages* buffer, before all the repetitions that couldn't be
> run while Emacs was suspended are run when we wake up.
>
> Apparently this is *not* a new behavior (I can reproduce it with
> Debian's 26.1) although I only recently started noticing it.
>
> If we decide to consider this a feature (I guess there can be
> circumstances where it might make sense, tho I'm not sure those would
> really work well with the way we handle timers), I think we should
> provide some way for users of timers to indicate whether they want to
> use this feature or not (and I think it makes sense to default to not
> using this feature).
I think you can already control this by customizing the value of
timer-max-repeats. It is 10 by default, so you should never see more
than 10 repetitions, no matter how long was Emacs suspended.
next prev parent reply other threads:[~2019-04-23 17:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-23 16:59 bug#35400: 27.0.50; Timers repeated after waking from suspend Stefan Monnier
2019-04-23 17:30 ` Eli Zaretskii [this message]
2021-02-02 14:34 ` Lars Ingebrigtsen
2021-02-02 15:32 ` Eli Zaretskii
2021-02-02 16:18 ` Stefan Monnier
2021-02-03 18:42 ` Lars Ingebrigtsen
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=834l6o4ok4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=35400@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.