From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#35400: 27.0.50; Timers repeated after waking from suspend Date: Tue, 02 Feb 2021 17:32:38 +0200 Message-ID: <83ft2e5vu1.fsf@gnu.org> References: <834l6o4ok4.fsf@gnu.org> <87y2g6lesc.fsf@gnus.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="32893"; mail-complaints-to="usenet@ciao.gmane.io" Cc: monnier@iro.umontreal.ca, 35400@debbugs.gnu.org To: Lars Ingebrigtsen Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue Feb 02 16:37:24 2021 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l6xk4-0008Pg-0y for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 02 Feb 2021 16:37:24 +0100 Original-Received: from localhost ([::1]:34894 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1l6xk3-000368-0f for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 02 Feb 2021 10:37:23 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:34776) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1l6xfq-0007Fj-TT for bug-gnu-emacs@gnu.org; Tue, 02 Feb 2021 10:33:02 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:52696) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1l6xfq-0007uA-KO for bug-gnu-emacs@gnu.org; Tue, 02 Feb 2021 10:33:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1l6xfq-0001x7-Fq for bug-gnu-emacs@gnu.org; Tue, 02 Feb 2021 10:33:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 02 Feb 2021 15:33:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 35400 X-GNU-PR-Package: emacs Original-Received: via spool by 35400-submit@debbugs.gnu.org id=B35400.16122799777492 (code B ref 35400); Tue, 02 Feb 2021 15:33:02 +0000 Original-Received: (at 35400) by debbugs.gnu.org; 2 Feb 2021 15:32:57 +0000 Original-Received: from localhost ([127.0.0.1]:36009 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1l6xfk-0001wg-QK for submit@debbugs.gnu.org; Tue, 02 Feb 2021 10:32:57 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:45044) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1l6xfi-0001wL-Tz for 35400@debbugs.gnu.org; Tue, 02 Feb 2021 10:32:56 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:48253) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1l6xfd-0007nn-4a; Tue, 02 Feb 2021 10:32:49 -0500 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:2216 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1l6xfV-0001w9-T9; Tue, 02 Feb 2021 10:32:44 -0500 In-Reply-To: <87y2g6lesc.fsf@gnus.org> (message from Lars Ingebrigtsen on Tue, 02 Feb 2021 15:34:11 +0100) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:199144 Archived-At: > From: Lars Ingebrigtsen > Cc: Stefan Monnier , 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?