* bug#10876: Please mention format-time-string in "Time of Day"
@ 2012-02-24 2:18 Lennart Borgman
2012-02-25 4:39 ` Chong Yidong
0 siblings, 1 reply; 4+ messages in thread
From: Lennart Borgman @ 2012-02-24 2:18 UTC (permalink / raw)
To: 10876
Please mention the function format-time-string in the elisp manual in
the chapter "Time of Day" (39.5 in my version here).
^ permalink raw reply [flat|nested] 4+ messages in thread
* bug#10876: Please mention format-time-string in "Time of Day"
2012-02-24 2:18 bug#10876: Please mention format-time-string in "Time of Day" Lennart Borgman
@ 2012-02-25 4:39 ` Chong Yidong
2012-02-25 5:01 ` Lennart Borgman
0 siblings, 1 reply; 4+ messages in thread
From: Chong Yidong @ 2012-02-25 4:39 UTC (permalink / raw)
To: Lennart Borgman; +Cc: 10876
Lennart Borgman <lennart.borgman@gmail.com> writes:
> Please mention the function format-time-string in the elisp manual in
> the chapter "Time of Day" (39.5 in my version here).
Please explain why you think it deserves a special mention. There are
three nodes all about handling times, one after the other; it is silly
to add links in every node to all the other neighboring nodes, unless
there is a particularly good reason.
^ permalink raw reply [flat|nested] 4+ messages in thread
* bug#10876: Please mention format-time-string in "Time of Day"
2012-02-25 4:39 ` Chong Yidong
@ 2012-02-25 5:01 ` Lennart Borgman
2012-03-17 14:00 ` Chong Yidong
0 siblings, 1 reply; 4+ messages in thread
From: Lennart Borgman @ 2012-02-25 5:01 UTC (permalink / raw)
To: Chong Yidong; +Cc: 10876
On Sat, Feb 25, 2012 at 05:39, Chong Yidong <cyd@gnu.org> wrote:
> Lennart Borgman <lennart.borgman@gmail.com> writes:
>
>> Please mention the function format-time-string in the elisp manual in
>> the chapter "Time of Day" (39.5 in my version here).
>
> Please explain why you think it deserves a special mention. There are
> three nodes all about handling times, one after the other; it is silly
> to add links in every node to all the other neighboring nodes, unless
> there is a particularly good reason.
format-time-string is similar to current-time-string, but more
flexible. So they should probably be mentioned in the same place.
However maybe a better suggestion is to move current-time-string to
"39.7 Parsing and Formatting Times" and add a link to 39.7 from 39.5?
(Actually I think the whole part about "date and time" should be a
little bit reorganized. Having a heading "Date and Time" (instead of
"Time of Day") and subheadings for "Time Conversion" and "Time
Parsing" looks better to me.)
^ permalink raw reply [flat|nested] 4+ messages in thread
* bug#10876: Please mention format-time-string in "Time of Day"
2012-02-25 5:01 ` Lennart Borgman
@ 2012-03-17 14:00 ` Chong Yidong
0 siblings, 0 replies; 4+ messages in thread
From: Chong Yidong @ 2012-03-17 14:00 UTC (permalink / raw)
To: Lennart Borgman; +Cc: 10876
Lennart Borgman <lennart.borgman@gmail.com> writes:
> format-time-string is similar to current-time-string, but more
> flexible. So they should probably be mentioned in the same place.
>
> However maybe a better suggestion is to move current-time-string to
> "39.7 Parsing and Formatting Times" and add a link to 39.7 from 39.5?
> (Actually I think the whole part about "date and time" should be a
> little bit reorganized. Having a heading "Date and Time" (instead of
> "Time of Day") and subheadings for "Time Conversion" and "Time
> Parsing" looks better to me.)
I have tweaked the text to make the connection clearer.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2012-03-17 14:00 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-02-24 2:18 bug#10876: Please mention format-time-string in "Time of Day" Lennart Borgman
2012-02-25 4:39 ` Chong Yidong
2012-02-25 5:01 ` Lennart Borgman
2012-03-17 14:00 ` Chong Yidong
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).