From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Michael Gauland <mikelygee@no8wireless.co.nz>
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: [new exporter] Date format string not handled for LaTeX export
Date: Tue, 30 Oct 2012 21:13:15 +0100 [thread overview]
Message-ID: <87pq3zoh0k.fsf@gmail.com> (raw)
In-Reply-To: <871ugf6bk3.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Tue, 30 Oct 2012 18:48:28 +0000")
Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> The problem with the inf-loop now makes sense but the documentation
> implies otherwise:
>
> ,----
> | Also,
> | `{{{date(FORMAT)}}}' and `{{{modification-time(FORMAT)}}}' refer to
> | current date time and to the modification time of the file being
> `----
I changed the date macro on purpose.
Since {{{title}}}, {{{author}}} and {{{email}}} refer to, respectively,
#+TITLE:, #+AUTHOR: and #+EMAIL:, {{{date}}} could as well refer to
#+DATE:.
For the sake of completeness, other hard-coded macros are
{{{property(name)}}}, {{{time(format-string)}}}, {{{input-file}}} and
{{{modification-time(format-string)}}}.
Regards,
next prev parent reply other threads:[~2012-10-30 20:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-29 3:41 [new exporter] Date format string not handled for LaTeX export Michael Gauland
2012-10-29 13:04 ` Nicolas Goaziou
2012-10-29 21:25 ` Michael Gauland
2012-10-29 21:46 ` Nicolas Goaziou
2012-10-29 22:55 ` Michael Gauland
2012-10-29 23:05 ` Nick Dokos
2012-10-30 7:14 ` Nicolas Goaziou
2012-10-30 8:29 ` Achim Gratz
2012-10-30 9:27 ` Nicolas Goaziou
2012-10-30 9:18 ` Michael Gauland
2012-10-30 9:29 ` Nicolas Goaziou
2012-10-30 16:43 ` Michael Gauland
2012-10-30 17:25 ` Nick Dokos
2012-10-30 18:01 ` Nicolas Goaziou
2012-10-30 22:24 ` Michael Gauland
2012-10-30 18:48 ` Eric S Fraga
2012-10-30 20:13 ` Nicolas Goaziou [this message]
2012-10-30 8:58 ` Eric S Fraga
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=87pq3zoh0k.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mikelygee@no8wireless.co.nz \
--cc=nicholas.dokos@hp.com \
/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.