GNU bug report logs - #67706
30.0.50; timer-next-integral-multiple-of-time does not account for different time-zones

Previous Next

Full log

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Bruno Boal <egomet <at> bboal.com>
Cc: 67706 <at> debbugs.gnu.org, info <at> protesilaos.com
Subject: Re: bug#67706: 30.0.50;
 timer-next-integral-multiple-of-time does not account for different
 time-zones
Date: Fri, 08 Dec 2023 14:44:36 +0200

> Cc: info <at> protesilaos.com
> From: Bruno Boal <egomet <at> bboal.com>
> Date: Fri, 08 Dec 2023 11:51:01 +0000
> 
> While trying the following snippet in both Lisbon and Athens, we
> get the same timer object as showed in list-timers.
> 
> (run-at-time t 14400 #'message "Testing")
> 
> What we would expect, is two different timer objects accounting for the
> different time zones.
> 
> We did a edebug and found out that the function aforementioned on the
> subject is always returning the same value despite of the different
> local times.
> 
> Are we missing something obvious or is this a bug?

Please show a minimal recipe, starting from "emacs -Q", to reproduce
the issue you are seeing.  I'm not sure I understand all the details,
and therefore don't follow why you expected two objects.

Thanks.

Previous Next

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