From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#39824: 26.2; timers sometimes stop working when coming back from sleep Date: Sun, 19 Apr 2020 19:46:58 +0300 Message-ID: <83h7xfifst.fsf@gnu.org> References: <83imhvijes.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="53743"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 39824@debbugs.gnu.org To: ndame Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sun Apr 19 18:52:55 2020 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 1jQDBf-000Dti-Dg for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 19 Apr 2020 18:52:55 +0200 Original-Received: from localhost ([::1]:44266 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jQDBe-0002ha-G1 for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 19 Apr 2020 12:52:54 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:45592 helo=eggs1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jQD6x-00005j-3y for bug-gnu-emacs@gnu.org; Sun, 19 Apr 2020 12:48:03 -0400 Original-Received: from Debian-exim by eggs1p.gnu.org with spam-scanned (Exim 4.90_1) (envelope-from ) id 1jQD6w-0001zu-OS for bug-gnu-emacs@gnu.org; Sun, 19 Apr 2020 12:48:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:34235) by eggs1p.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1jQD6w-0001zA-Bm for bug-gnu-emacs@gnu.org; Sun, 19 Apr 2020 12:48:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1jQD6w-0002eo-A1 for bug-gnu-emacs@gnu.org; Sun, 19 Apr 2020 12:48:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 19 Apr 2020 16:48:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 39824 X-GNU-PR-Package: emacs Original-Received: via spool by 39824-submit@debbugs.gnu.org id=B39824.158731483210156 (code B ref 39824); Sun, 19 Apr 2020 16:48:02 +0000 Original-Received: (at 39824) by debbugs.gnu.org; 19 Apr 2020 16:47:12 +0000 Original-Received: from localhost ([127.0.0.1]:45781 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1jQD68-0002dj-7Z for submit@debbugs.gnu.org; Sun, 19 Apr 2020 12:47:12 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:42462 helo=eggs1p.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1jQD66-0002dX-Ns for 39824@debbugs.gnu.org; Sun, 19 Apr 2020 12:47:11 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:53653) by eggs1p.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jQD61-0000yU-EX; Sun, 19 Apr 2020 12:47:05 -0400 Original-Received: from [176.228.60.248] (port=3146 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1jQD60-0001Mq-O9; Sun, 19 Apr 2020 12:47:05 -0400 In-Reply-To: (message from ndame on Sun, 19 Apr 2020 15:54:51 +0000) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-Received-From: 209.51.188.43 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:178656 Archived-At: > Date: Sun, 19 Apr 2020 15:54:51 +0000 > From: ndame > Cc: "39824@debbugs.gnu.org" <39824@debbugs.gnu.org> > > Anyway, I just wanted to explain which you asked earlier: "So the > main question to be answered is: how come that t remained in the timer? Thanks, but it still remains to be shown that the offending timer (the real-life one) did indeed signal an error, or at least could have.