OK, here is a patch that tries to do that.
All the best,
Tom
Kaushal <kaushal.m...@gmail.com> writes:
> Yeah, the documentation definitely needs refining.
>
> {{{date}}} / {{{date(FORMAT)}}} [FORMAT is optional] - Inserts the
> #+DATE keyword value;
> optionally formats as per FORMAT (Refer `format-time-string` function for
> syntax.){{{time(FORMAT)}}} - Inserts the current time stamp as per the
> FORMAT {{{modification-time(FORMAT)}}} - Inserts modification time of the
> file being exported as per the FORMAT
>From cf8ba2d13a4b733e358b28fe2ad8d83f0018fca9 Mon Sep 17 00:00:00 2001
From: tsdye <t...@tsdye.com>
Date: Thu, 6 Aug 2015 10:47:07 -1000
Subject: [PATCH] Edit date and time macros
---
doc/org.texi | 14 ++++++++------
1 file changed, 8 insertions(+), 6 deletions(-)
diff --git a/doc/org.texi b/doc/org.texi
index d420259..b5ababb 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -10217,15 +10217,17 @@ export.
@item @{@{@{date@}@}@}
@itemx @{@{@{date(@var{FORMAT})@}@}@}
@itemx @{@{@{time(@var{FORMAT})@}@}@}
-@itemx @{@{@{modification-time(@var{FORMAT})@}@}@}
@cindex date, macro
@cindex time, macro
-@cindex modification time, macro
-These macros refer to the @code{#+DATE} keyword, the current date, and the
-modification time of the file being exported, respectively. @var{FORMAT}
+These macros refer to information associated with the @code{#+DATE} keyword.
+The @var{FORMAT} argument, which is optional for the @{@{@{date@}@}@} macro,
should be a format string understood by @code{format-time-string}. Note that
-@var{FORMAT} is an optional argument to the @code{@{@{@{date@}@}@}} macro,
-and that it will only be used if @code{#+DATE} is a single timestamp.
+it will only be used if @code{#+DATE} is a single timestamp.
+
+@itemx @{@{@{modification-time(@var{FORMAT})@}@}@}
+@cindex modification time, macro
+
+This macro refers to the modification time of the file being exported.
@item @{@{@{input-file@}@}@}
@cindex input file, macro
--
2.4.5
--
Thomas S. Dye
http://www.tsdye.com
