From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Michael Gauland <mikelygee@no8wireless.co.nz>
Cc: emacs-orgmode@gnu.org
Subject: Re: [new exporter] Date format string not handled for LaTeX export
Date: Mon, 29 Oct 2012 14:04:37 +0100 [thread overview]
Message-ID: <87fw4xqviy.fsf@gmail.com> (raw)
In-Reply-To: <loom.20121029T043830-630@post.gmane.org> (Michael Gauland's message of "Mon, 29 Oct 2012 03:41:18 +0000 (UTC)")
Hello,
Michael Gauland <mikelygee@no8wireless.co.nz> writes:
> When I provide a format string to the #+DATE: option, the old LaTeX exporter
> correctly uses it to format the current date; the new exporter just uses the
> format string for the date.
I wasn't aware of that "feature". Though, I don't like it: it is fragile
for technical reasons (it may or may not work on every exporter) and it
adds yet another special rule to remember.
On the other hand, you have a hard-coded macro to solve this problem:
#+DATE: {{{time(%c)}}}
It will work across every back-end (but you need the latest Org version,
since I recently to fixed a bug related to it).
> The new HTML exporter does not have this problem.
I am going to remove this hack from new back-ends as it isn't necessary.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2012-10-29 13:07 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 [this message]
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
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fw4xqviy.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mikelygee@no8wireless.co.nz \
/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/org-mode.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).