unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: monnier@iro.umontreal.ca, 35400@debbugs.gnu.org
Subject: bug#35400: 27.0.50; Timers repeated after waking from suspend
Date: Tue, 02 Feb 2021 17:32:38 +0200	[thread overview]
Message-ID: <83ft2e5vu1.fsf@gnu.org> (raw)
In-Reply-To: <87y2g6lesc.fsf@gnus.org> (message from Lars Ingebrigtsen on Tue,  02 Feb 2021 15:34:11 +0100)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: Stefan Monnier <monnier@iro.umontreal.ca>,  35400@debbugs.gnu.org
> Date: Tue, 02 Feb 2021 15:34:11 +0100
> 
> > 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.
> 
> Right, so the only question here is whether to change the value of that
> variable (to not repeat).  I think that would certainly be less
> surprising, but I'm not sure whether that would break people's code or
> not?

There are two use cases here.  One is the one we have been discussing:
when Emacs wakes from suspension, or the machine wakes from sleep.
The other is that somehow Emacs didn't get CPU to run, due to some
expensive processing on the system.  It might be that people expect
timers not to try to make up for the sleep or suspension period, but
they may want them to make up for the second use case.

So maybe this should be a property of the timer itself?  Or maybe the
time elapsed since the last timer invocation should be the factor upon
which to decide whether to run more than once or not?





  reply	other threads:[~2021-02-02 15:32 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
2021-02-02 14:34   ` Lars Ingebrigtsen
2021-02-02 15:32     ` Eli Zaretskii [this message]
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

  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=83ft2e5vu1.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=35400@debbugs.gnu.org \
    --cc=larsi@gnus.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 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).