all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Bruno Boal <egomet@bboal.com>
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 22:45:50 +0200	[thread overview]
Message-ID: <837clozam9.fsf@gnu.org> (raw)
In-Reply-To: <87fs0c32d9.fsf@bboal.com> (message from Bruno Boal on Fri, 08 Dec 2023 19:45:06 +0000)

> 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.





  reply	other threads:[~2023-12-08 20:45 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 [this message]
2023-12-08 21:00           ` Bruno Boal
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=837clozam9.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=67706@debbugs.gnu.org \
    --cc=egomet@bboal.com \
    --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.