From: <tomas@tuxteam.de>
To: Emanuel Berg <embe8573@student.uu.se>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Minibuffer tray to display current time and date
Date: Fri, 24 Apr 2015 16:13:19 +0200 [thread overview]
Message-ID: <20150424141319.GA19093@tuxteam.de> (raw)
In-Reply-To: <874mo6bgzx.fsf@debian.uxu>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Fri, Apr 24, 2015 at 12:46:10AM +0200, Emanuel Berg wrote:
> jorge.alfaro-murillo@yale.edu (Jorge A.
> Alfaro-Murillo) writes:
>
> > Optimal would be to run now, and then (run-at-time
> > NEXT-TIME-MINUTE-CHANGES nil (lambda () (run-at-time
> > t 60 ...
>
> Are you thinking like this: "The granularity of the
> clock is 1 minute. So it should be updated once every
> minute, i.e. every 60 seconds."
>
> That sounds a bit risky to me, so I'd recommend setting
> it so that it will be set somewhere around three times
> per minute - and not set evenly so, but for example
> every 22 seconds:
>
> 0, 22, 44, 6 (66), 28, 50, ...
This sounds a bit roundabout: why not run-at-time? Do you fear
that it gets out of sync?
Regards
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlU6T38ACgkQBcgs9XrR2kZ1UwCaA8qCltmKECaI3v+Ytyg0kjCk
eWUAn1OPn7/n/xOpHq6zIB4dJztEDIZW
=I6Cv
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2015-04-24 14:13 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-22 16:07 Minibuffer tray to display current time and date Alexander Shukaev
2015-04-22 16:11 ` Eli Zaretskii
2015-04-22 16:17 ` Alexander Shukaev
2015-04-22 16:57 ` Michael Heerdegen
2015-04-22 17:05 ` Stefan Monnier
[not found] ` <mailman.1379.1429722347.904.help-gnu-emacs@gnu.org>
2015-04-23 0:59 ` Emanuel Berg
2015-04-23 15:15 ` Jorge A. Alfaro-Murillo
[not found] ` <mailman.1461.1429802140.904.help-gnu-emacs@gnu.org>
2015-04-23 15:43 ` Emanuel Berg
2015-04-23 18:11 ` Jorge A. Alfaro-Murillo
[not found] ` <mailman.1474.1429812715.904.help-gnu-emacs@gnu.org>
2015-04-23 22:46 ` Emanuel Berg
2015-04-24 14:13 ` tomas [this message]
2015-04-24 14:41 ` Eli Zaretskii
2015-04-24 14:57 ` Jorge A. Alfaro-Murillo
2015-04-24 16:48 ` Eli Zaretskii
2015-04-24 20:18 ` Jorge A. Alfaro-Murillo
[not found] ` <mailman.1562.1429906736.904.help-gnu-emacs@gnu.org>
2015-04-25 1:11 ` Dan Espen
2015-04-26 2:38 ` Jorge A. Alfaro-Murillo
2015-04-26 14:48 ` Eli Zaretskii
2015-04-26 15:52 ` tomas
2015-04-26 16:05 ` Eli Zaretskii
2015-04-27 0:36 ` Stefan Monnier
2015-04-28 17:27 ` Alexander Shukaev
2015-04-28 17:30 ` Eli Zaretskii
2015-04-28 17:32 ` Alexander Shukaev
2015-04-28 17:55 ` Eli Zaretskii
2015-04-29 0:53 ` Stefan Monnier
[not found] ` <mailman.1824.1430242034.904.help-gnu-emacs@gnu.org>
2015-04-28 17:58 ` Emanuel Berg
2015-04-29 0:55 ` Stefan Monnier
2015-05-01 4:49 ` Alexander Shukaev
2015-05-01 4:54 ` Alexander Shukaev
2015-05-06 10:31 ` Alexander Shukaev
2015-05-06 12:49 ` Stefan Monnier
2015-05-12 11:34 ` Alexander Shukaev
2015-05-14 19:44 ` Stefan Monnier
2015-06-25 19:18 ` Alexander Shukaev
[not found] ` <mailman.2858.1431430470.904.help-gnu-emacs@gnu.org>
2015-05-12 17:24 ` Emanuel Berg
[not found] ` <mailman.1537.1429888188.904.help-gnu-emacs@gnu.org>
2015-04-25 1:16 ` Emanuel Berg
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=20150424141319.GA19093@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=embe8573@student.uu.se \
--cc=help-gnu-emacs@gnu.org \
/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.
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).