From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Org mailing list <emacs-orgmode@gnu.org>
Subject: Re: How to expand macro in LaTeX export? How to use different options per export type?
Date: Wed, 31 Mar 2021 11:45:36 +0100 [thread overview]
Message-ID: <87zgyjfvov.fsf@ucl.ac.uk> (raw)
In-Reply-To: <YGRO97i+/7zMrbsl@protected.localdomain> (Jean Louis's message of "Wed, 31 Mar 2021 13:29:11 +0300")
On Wednesday, 31 Mar 2021 at 13:29, Jean Louis wrote:
> By doing this:
>
> @@latex:\def\version{@@ {{{version}}} @@latex:}@@
>
> Then {{{version}}} will get expanded in the document, right? As I have
> hidden then only tags surrounding {{{version}}}.
Yes.
>> Also, a macro can itself use the @@ directive to provide alternate
>> versions for LaTeX and HTML, as in
>>
>> #+macro: blah @@html:some HTML code@@@@latex: some LaTeX code@@
>
> I have tried this:
>
> #+OPTIONS: @@html:title:t toc:t@@ @@latex:title:nil toc:nil@@ todo:nil
>
> But it is not working in options. It would be good if it works in OPTIONS.
The reason it can work in the macro but not for options is that the
macro is expanded into the text and then the text is processed as normal
text so the @@ directives are processed. The options line does not go
through the same processing.
--
: Eric S Fraga via Emacs 28.0.50, Org release_9.4.4-254-g37749c
next prev parent reply other threads:[~2021-03-31 10:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-31 9:40 How to expand macro in LaTeX export? How to use different options per export type? Jean Louis
2021-03-31 10:03 ` Eric S Fraga
2021-03-31 10:29 ` Jean Louis
2021-03-31 10:45 ` Eric S Fraga [this message]
2021-03-31 11:04 ` Jean Louis
2021-03-31 12:30 ` Eric S Fraga
2021-03-31 11:32 ` Greg Minshall
2021-03-31 20:04 ` Jean Louis
2021-04-01 3:47 ` Greg Minshall
2021-04-01 4:44 ` Greg Minshall
2021-04-03 21:57 ` Juan Manuel Macías
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=87zgyjfvov.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
/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).