Re: org-html-postamble-format and #+DATE: specification in 8.0pre

[Dieter Wilhelm <dieter@duenenhof-wilhelm.de>]

Nicolas Goaziou <n.goaziou@gmail.com> writes:

> Hello,
>
>> Sorry I don't get it completely.  
>> I'd like to have as the DATE value the current change time of the file.
>> You mean that I should set this with the Emacs timestamp facility? Like:
>
>> #+DATE: Time-stamp: " "
>
> If you're exporting a buffer associated to a file, you may use:
>
>   #+DATE: {{{modification-time(%Y-%m-%d)}}}

Thank you for the explanation, I really appreciate that and I'm happy to
learn new possibilities in org.  At first I thought it just a regression
that I had additionally to put in a macro but on the other hand it is
much more precise for my needs then

#+DATE %Y-%m-%d

which gave me in 7.xx only the current time.  So far so good.

#+DATE: {{{modification-time(%Y-%m-%d)}}}

is working when I'm exporting individual files but now when I'm trying
to publish I'm getting:

Generating tree-style sitemap for Die Dünenhof-Seite [15 times]
byte-code: Bad timestamp `((macro (:key modification-time :value {{{modification-time(%Y-%m-%d)}}} :args (%Y-%m-%d) :begin 1 :end 34 :post-blank 0 :parent #0)))'
Error was: (stringp ((macro (:key modification-time :value {{{modification-time(%Y-%m-%d)}}} :args (%Y-%m-%d) :begin 1 :end 34 :post-blank 0 :parent #1))))

Seemingly this macro wreaks havoc with the automatic sitemap
generation...

Thanks

        Dieter


>
> Regards,

-- 
Best wishes

H. Dieter Wilhelm
Darmstadt
Germany