From: Bruno Boal <egomet@bboal.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 67706@debbugs.gnu.org, info@protesilaos.com
Subject: bug#67706: 30.0.50; timer-next-integral-multiple-of-time does not account for different time-zones
Date: Fri, 08 Dec 2023 21:00:31 +0000 [thread overview]
Message-ID: <87ttosz9xs.fsf@bboal.com> (raw)
In-Reply-To: <837clozam9.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Bruno Boal <egomet@bboal.com>
>> Cc: 67706@debbugs.gnu.org, info@protesilaos.com
>> Date: Fri, 08 Dec 2023 19:45:06 +0000
>>
>> (run-at-time TIME REPEAT FUNCTION &rest ARGS)
>> ...
>> TIME should be one of: ...
>>
>> - a number of seconds from now; ;; The example you gave. Not applicable.
>>
>> - or t (with non-nil REPEAT) meaning the next integral multiple of
>> REPEAT. This is handy when you want the function to run at a certain
>> "round" number. For instance, (run-at-time t 60 ...) will run at
>> 11:04:00, 11:05:00, etc. ;; My example.
>
> 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.
Best regards,
Bruno Boal
next prev parent reply other threads:[~2023-12-08 21:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 11:51 bug#67706: 30.0.50; timer-next-integral-multiple-of-time does not account for different time-zones Bruno Boal
2023-12-08 12:44 ` Eli Zaretskii
2023-12-08 16:51 ` Bruno Boal
2023-12-08 19:29 ` Eli Zaretskii
2023-12-08 19:45 ` Bruno Boal
2023-12-08 20:45 ` Eli Zaretskii
2023-12-08 21:00 ` Bruno Boal [this message]
2023-12-09 7:20 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ttosz9xs.fsf@bboal.com \
--to=egomet@bboal.com \
--cc=67706@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=info@protesilaos.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.