Hello,
Nick Dokos nicholas.do...@hp.com writes:
Michael Gauland mikely...@no8wireless.co.nz wrote:
Nicolas Goaziou n.goaziou at gmail.com writes:
I just tried with a minimal init and it worked. Could you send the
example you're trying to export?
The file is below. With a minimal
Nicolas Goaziou writes:
{{{date(%c)}}} is another macro that is replaced with the #+DATE: value
during export. Since you try to replace #+DATE: value with itself, you
dive into an inf loop.
Which raises the question if this shouldn't be detected and prevented,
at least if direct recursion is
On 30/10/12 20:14, Nicolas Goaziou wrote:
This is {{{time(...)}}}, not {{{date(...)}}}.
{{{date(%c)}}} is another macro that is replaced with the #+DATE: value
during export. Since you try to replace #+DATE: value with itself, you
dive into an inf loop.
I think I understand what's going on
Hello,
Achim Gratz strom...@nexgo.de writes:
Nicolas Goaziou writes:
{{{date(%c)}}} is another macro that is replaced with the #+DATE: value
during export. Since you try to replace #+DATE: value with itself, you
dive into an inf loop.
Which raises the question if this shouldn't be detected
Michael Gauland mikely...@no8wireless.co.nz writes:
I think I understand what's going on now, but I'm still at a loss as to
how to get the date I want. Can I tell the exporter that the date on the
document should be derived from the current time (or the last
modification time), formatted a
Nick Dokos nicholas.do...@hp.com writes:
With a minimal file, I get a cpu pegged at 100% with no end in
sight. Setting debug-on-quit and C-g gives me the following backtrace.
I get this same problem (100% cpu) if I use the date macro in the #+DATE
line; I don't get this if I use the
On 30/10/12 22:29, Nicolas Goaziou wrote:
Doesn't
#+DATE: {{{time(%Y-%m-%d %H:%M)}}}
get you what you expect?
That gives me an empty date string.
signature.asc
Description: OpenPGP digital signature
Michael Gauland mikely...@no8wireless.co.nz wrote:
On 30/10/12 22:29, Nicolas Goaziou wrote:
Doesn't
#+DATE: {{{time(%Y-%m-%d %H:%M)}}}
get you what you expect?
That gives me an empty date string.
Works for me.
Nick
PS Re: the infinite loop with date() - D'oh! That's what I
Hello,
Nick Dokos nicholas.do...@hp.com writes:
Michael Gauland mikely...@no8wireless.co.nz wrote:
On 30/10/12 22:29, Nicolas Goaziou wrote:
Doesn't
#+DATE: {{{time(%Y-%m-%d %H:%M)}}}
get you what you expect?
That gives me an empty date string.
Works for me.
I also get a
Nicolas Goaziou n.goaz...@gmail.com writes:
Michael Gauland mikely...@no8wireless.co.nz writes:
How can I set #+DATE to get an equivalent result?
Doesn't
#+DATE: {{{time(%Y-%m-%d %H:%M)}}}
Works perfectly fine for me. And thanks for the explanation of the
cause of the inf-loop!
The
Eric S Fraga e.fr...@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
Nicolas Goaziou n.goaziou at gmail.com writes:
Hello,
Nick Dokos nicholas.dokos at hp.com writes:
Works for me.
I also get a correct date with it, even with a minimal set-up.
Well, this is embarassing. I tackled it fresh, after a cup of coffee (for me)
and a re-start (emacs), and
Hello,
Michael Gauland mikely...@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
Nicolas Goaziou n.goaziou at gmail.com writes:
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).
Thanks--that will do
Michael Gauland mikely...@no8wireless.co.nz writes:
Nicolas Goaziou n.goaziou at gmail.com writes:
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
Nicolas Goaziou n.goaziou at gmail.com writes:
I just tried with a minimal init and it worked. Could you send the
example you're trying to export?
The file is below. With a minimal init, I get the error Symbol's function
definition is void: org-macro-initialize-templates'. If I use my full
Michael Gauland mikely...@no8wireless.co.nz wrote:
Nicolas Goaziou n.goaziou at gmail.com writes:
I just tried with a minimal init and it worked. Could you send the
example you're trying to export?
The file is below. With a minimal init, I get the error Symbol's function
definition is
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.
The new HTML exporter does not have this problem.
18 matches
Mail list logo
