From: Lars Ingebrigtsen <larsi@gnus.org>
To: Arthur Miller <arthur.miller@live.com>
Cc: 52235@debbugs.gnu.org
Subject: bug#52235: 29.0.50; Suggestion: refactor time.el into a more general 'clock' framework
Date: Thu, 02 Dec 2021 09:29:44 +0100 [thread overview]
Message-ID: <87r1avmmtj.fsf@gnus.org> (raw)
In-Reply-To: <DB9PR09MB49867F87628009D4F53B756E96689@DB9PR09MB4986.eurprd09.prod.outlook.com> (Arthur Miller's message of "Thu, 02 Dec 2021 00:08:37 +0100")
Arthur Miller <arthur.miller@live.com> writes:
> My idea to per-use it is to simply run 'update-hooks' on clock beat,
> so any application can register a hook that will be called on a "clock
> beat". While it is maybe not so super-synchronized with system clock,
> it still gives impression of clocks in Emacs be synchronized.
If I understand correctly, by "clock beat" you mean an integer multiple
of some time? timer.el didn't support that well previously, but this
was fixed a few months ago (in 50765f3f) with TIME:
- or t (with non-nil REPEAT) meaning the next integral
multiple of REPEAT.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-12-02 8:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <DB9PR09MB49867F87628009D4F53B756E96689@DB9PR09MB4986.eurprd09.prod.outlook.com>
2021-12-02 7:26 ` bug#52235: 29.0.50; Suggestion: refactor time.el into a more general 'clock' framework Eli Zaretskii
2021-12-02 9:19 ` Arthur Miller
2021-12-02 9:55 ` Eli Zaretskii
2021-12-02 23:48 ` Arthur Miller
2021-12-02 8:29 ` Lars Ingebrigtsen [this message]
2021-12-02 9:28 ` Arthur Miller
2021-12-02 9:55 ` Lars Ingebrigtsen
2021-12-02 23:36 ` Arthur Miller
2021-12-03 16:23 ` Lars Ingebrigtsen
2021-12-03 0:52 ` Stefan Kangas
2021-12-03 7:26 ` 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r1avmmtj.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=52235@debbugs.gnu.org \
--cc=arthur.miller@live.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).