From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 25112@debbugs.gnu.org
Subject: bug#25112: 24.5; function to encode time from time string
Date: Mon, 5 Dec 2016 13:49:56 -0800 (PST) [thread overview]
Message-ID: <62e0bec4-0ffd-49f9-b8be-577c40882399@default> (raw)
In-Reply-To: <<83vauyjr3g.fsf@gnu.org>>
> > Enhancement request: Please add a function that accepts a time
> > string and a format spec (to interpret the time string), and
> > returns a time value that represents the same time.
>
> I believe you want either date-to-time or parse-time-string (the
> former is just a thin wrapper around the latter). date-to-time is
> described in the ELisp manual.
Sheesh. Dunno how I missed `date-to-time' in the manual. I read
the 3 nodes about dates & times, but clearly I didn't read them
well enough.
Maybe it would help to mention this direction of conversion after
the second paragraph of node `Time of Day', with a cross-reference?
And maybe the node named `Time Conversion' should mention something
about conversion both directions between strings and times, with
cross-references?
Anyway, `date-to-time' does what I want (though it seems to give
only a 2-element list, at least in the cases I've tried).
Its name does NOT seem very good, though. Among other things,
either a date or a time can be represented as either a list or
a string - neither is inherently only one or the other.
It might help to say something like:
(current-time-string (date-to-time date-time-string)) =
date-time-string
and
(date-to-time (current-time-string date-time-list)) =
date-time-list
Or if these are not always strictly true then at least point out
that this is the general idea.
E.g.,
(current-time-string (date-to-time "Sun Nov 27 16:38:38 2016")) =
"Sun Nov 27 16:38:38 2016"
(date-to-time (current-time-string '(22587 31886))) = (22587 31886)
I will close this bug, in any case. Thx.
next parent reply other threads:[~2016-12-05 21:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<5b95d9b8-3281-40da-872d-1a98b8a3d1fa@default>
[not found] ` <<83vauyjr3g.fsf@gnu.org>
2016-12-05 21:49 ` Drew Adams [this message]
2016-12-04 20:56 bug#25112: 24.5; function to encode time from time string Drew Adams
2016-12-04 21:50 ` Drew Adams
2016-12-05 16:08 ` 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=62e0bec4-0ffd-49f9-b8be-577c40882399@default \
--to=drew.adams@oracle.com \
--cc=25112@debbugs.gnu.org \
--cc=eliz@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.
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).