unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Stefan Monnier <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 15:34:11 +0100	[thread overview]
Message-ID: <87y2g6lesc.fsf@gnus.org> (raw)
In-Reply-To: <834l6o4ok4.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 23 Apr 2019 20:30:19 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> 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.

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?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2021-02-02 14:34 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 [this message]
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

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