GNU bug report logs - #52235
29.0.50; Suggestion: refactor time.el into a more general 'clock' framework

Previous Next

Full log

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

From: Arthur Miller <arthur.miller <at> live.com>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: 52235 <at> debbugs.gnu.org
Subject: Re: bug#52235: 29.0.50; Suggestion: refactor time.el into a more
 general 'clock' framework
Date: Thu, 02 Dec 2021 10:28:01 +0100

Lars Ingebrigtsen <larsi <at> gnus.org> writes:

> Arthur Miller <arthur.miller <at> 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?
I am not sure if we speak about same thing; but I mean the clock, synchronized
with what Emacs shows as time.

Also there is no read to run several timers when one timer could
be fine to run several hooks as well as saving some code repetition.

> was fixed a few months ago (in 50765f3f) with TIME:
>
> - or t (with non-nil REPEAT) meaning the next integral
>   multiple of REPEAT.

Previous Next

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