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 #28 received at 67706-done <at> debbugs.gnu.org (full text, mbox):

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

> From: Bruno Boal <egomet <at> bboal.com>
> Cc: 67706 <at> debbugs.gnu.org, info <at> protesilaos.com
> Date: Fri, 08 Dec 2023 21:00:31 +0000
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> > The ELisp manual says:
> >
> >
> >      In most cases, REPEAT has no effect on when _first_ call takes
> >      place--TIME alone specifies that.  There is one exception: if TIME
> >      is ‘t’, then the timer runs whenever the time is a multiple of
> >      REPEAT seconds after the epoch.
> >
> > So I think time in this case is measured since the epoch, which is
> > independent of the time zone.
> 
> I see. So it's desired behavior and not a bug. We'll have to work around
> it with code, since there's no option in run-at-time that fits our
> needs.
> 
> Thank you for the explanation, it's a closed issue to me.

Thanks, I'm therefore closing this bug.

Previous Next

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