From: storm@cua.dk (Kim F. Storm)
Cc: rudalics@gmx.at, cyd@stupidchicken.com, emacs-devel@gnu.org
Subject: Re: jit-lock timer etc.
Date: Thu, 24 Aug 2006 09:47:01 +0200 [thread overview]
Message-ID: <m3ac5u60ei.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <E1GG7dx-0004yv-6m@fencepost.gnu.org> (Richard Stallman's message of "Thu, 24 Aug 2006 01:20:41 -0400")
Richard Stallman <rms@gnu.org> writes:
> I can hardly imagine emacs being idle for more than 2^28 seconds, so
> it seems safe to simplify it to return a cons (SECS . USECS) [see patch below]
>
> I don't want to do that, because it would be incompatible with other
> time values.
Well, since this is primarily for use in connection with run-with-idle-timer,
it seems more logical to use something which can be used more or less
directly with that function.
> I'd rather people use time-to-seconds to convert.
time-to-seconds is in time-date.el which isn't pre-loaded.
If we stick to the current value of current-idle-time, should we move
time-to-seconds to subr.el?
>
> However, returning the value in floating point might be a good method.
That would be much better and cleaner, IMO.
And we can leave time-to-seconds where it is!
> But if we do that, we should call it float-idle-time.
Why?
The current name isn't list-with-three-elements-idle-time :-)
The doc string will tell that the return value is a float.
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2006-08-24 7:47 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-21 11:12 jit-lock timer etc Richard Stallman
2006-08-21 11:39 ` Kim F. Storm
2006-08-21 16:57 ` martin rudalics
2006-08-21 18:51 ` Chong Yidong
2006-08-21 22:22 ` martin rudalics
2006-08-21 23:26 ` Chong Yidong
2006-08-22 7:18 ` Kim F. Storm
2006-08-22 15:41 ` Richard Stallman
2006-08-23 12:27 ` martin rudalics
2006-08-23 13:09 ` Kim F. Storm
2006-08-24 5:20 ` Richard Stallman
2006-08-24 7:47 ` Kim F. Storm [this message]
2006-08-24 7:58 ` Kim F. Storm
2006-08-24 9:07 ` Kim F. Storm
2006-08-24 14:47 ` Chong Yidong
2006-08-25 20:23 ` Richard Stallman
2006-08-25 22:45 ` Kim F. Storm
2006-08-25 20:23 ` Richard Stallman
2006-08-25 21:27 ` Chong Yidong
2006-08-26 12:22 ` Richard Stallman
2006-08-24 9:10 ` Kim F. Storm
2006-08-24 12:23 ` martin rudalics
2006-08-24 12:54 ` Kim F. Storm
2006-08-24 13:07 ` Kim F. Storm
2006-08-24 13:11 ` Kim F. Storm
2006-08-24 13:34 ` Kim F. Storm
2006-08-24 18:11 ` martin rudalics
2006-08-24 20:11 ` Kim F. Storm
2006-08-24 23:41 ` Chong Yidong
2006-08-25 7:17 ` Kim F. Storm
2006-08-24 14:16 ` Chong Yidong
2006-08-24 5:20 ` Richard Stallman
2006-08-24 7:48 ` Kim F. Storm
2006-08-24 12:21 ` martin rudalics
2006-08-24 15:27 ` Chong Yidong
2006-08-24 15:40 ` Chong Yidong
2006-08-24 18:09 ` martin rudalics
2006-08-24 19:16 ` Stefan Monnier
2006-08-24 19:20 ` Stefan Monnier
2006-08-24 16:18 ` martin rudalics
2006-08-24 16:34 ` Chong Yidong
2006-08-24 19:48 ` Chong Yidong
2006-08-25 6:00 ` martin rudalics
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=m3ac5u60ei.fsf@kfs-l.imdomain.dk \
--to=storm@cua.dk \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=rudalics@gmx.at \
/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.