GNU bug report logs - #39824
26.2; timers sometimes stop working when coming back from sleep

Previous Next

Package: emacs;

Reported by: ndame <emacsuser <at> freemail.hu>

Date: Fri, 28 Feb 2020 15:57:01 UTC

Severity: normal

Tags: notabug

Found in version 26.2

Done: Stefan Kangas <stefan <at> marxist.se>

Bug is archived. No further changes may be made.

Full log


Message #56 received at 39824 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: ndame <ndame <at> protonmail.com>, ndame <ndame <at> protonmail.com>
Cc: 39824 <at> debbugs.gnu.org
Subject: Re: bug#39824: 26.2;
 timers sometimes stop working when coming back from sleep
Date: Sun, 19 Apr 2020 18:28:59 +0300
> Date: Sun, 19 Apr 2020 13:59:23 +0000
> From: ndame via "Bug reports for GNU Emacs,
>  the Swiss army knife of text editors" <bug-gnu-emacs <at> gnu.org>
> 
> If you run a timer with an error:
> 
> (run-with-timer 0 1 (lambda ()
>                       (print garbage)))
> 
> then the backtrace window comes up. If you press q there then you'll have a negative timer 
> in the list.
> 
> This probably is because function timer-event-handler uses condition-case-unless-debug, 
> so if you  press q then you go back to top level and the rest of the code doesn't run.
> 
> I understand condition-case-unless-debug is used, so one can debug a timer, but on the 
> other hand if debug is on for some other reason and the user press q  automatically
> to get rid of the backtrace window then the timer list will have some garbage in it.

If a timer signals an error, it is TRT to disable it, right?
Otherwise, it will keep signaling errors over and over and over again,
right?




This bug report was last modified 4 years and 273 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.