From: Paul Eggert <eggert@cs.ucla.edu>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: emacs-devel@gnu.org
Subject: Re: Subsecond decoded-time again
Date: Sun, 29 Sep 2019 11:09:30 -0500 [thread overview]
Message-ID: <6e4d5d00-847b-4d5e-09d5-63b13b5c1c97@cs.ucla.edu> (raw)
In-Reply-To: <87v9tbnz83.fsf@gnus.org>
On 9/29/19 6:01 AM, Lars Ingebrigtsen wrote:
> I thought I remembered that we settled on giving a special parameter to
> `decode-time' to make it return the sub-second bits, too?
Yes, it's the optional new FORM parameter of decode-time. E.g,,
(decode-time '(1566009571321 . 1000) t t) yields ((31321 . 1000) 39 2 17
8 2019 6 nil 0). This example is taken from the manual.
next prev parent reply other threads:[~2019-09-29 16:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-29 11:01 Subsecond decoded-time again Lars Ingebrigtsen
2019-09-29 16:09 ` Paul Eggert [this message]
2019-09-29 16:14 ` Lars Ingebrigtsen
2019-09-29 18:19 ` Paul Eggert
2019-09-29 18:48 ` Lars Ingebrigtsen
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=6e4d5d00-847b-4d5e-09d5-63b13b5c1c97@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.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.
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).