On Apr 22, 2009, at 10:17 AM, Daniel Clemente wrote:
El dc, abr 15 2009, Carsten Dominik va escriure:
just like [TABLE-OF-CONTENTS] inserts the table of contents, are
there other
variables which will be translated on export? For instance
[EXPORT-DATE] to
get the export date, [VERSION] for
El dc, abr 15 2009, Carsten Dominik va escriure:
>> just like [TABLE-OF-CONTENTS] inserts the table of contents, are there other
>> variables which will be translated on export? For instance [EXPORT-DATE] to
>> get the export date, [VERSION] for the Org version, [FILE-NAME] for this
>> file's na
If you make me a complete list of what you'd like to have, I
can add them to the macros. I don't want to add more [NAME],
I don't think it is "strange" enough.
- Carsten
On Apr 14, 2009, at 9:08 PM, Daniel Clemente wrote:
Hi,
just like [TABLE-OF-CONTENTS] inserts the table of contents, ar
Hi,
just like [TABLE-OF-CONTENTS] inserts the table of contents, are there other
variables which will be translated on export? For instance [EXPORT-DATE] to get
the export date, [VERSION] for the Org version, [FILE-NAME] for this file's
name, …
Otherwise, dynamic blocks with LISP code can
