From: Jean Louis <bugs@gnu.support>
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 14:04:49 +0300 [thread overview]
Message-ID: <YGRXUTvE2RMpxgqz@protected.localdomain> (raw)
In-Reply-To: <87zgyjfvov.fsf@ucl.ac.uk>
* Eric S Fraga <e.fraga@ucl.ac.uk> [2021-03-31 13:46]:
> 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.
OK yet it is not doing what I need. The LaTeX definition of new
command is there because I cannot expand macro in LaTeX export
block. But nothing from that definition helps me in HTML.
Another solution could be if a program in BEGIN_SRC block could
generate Org inline, so that it gets processed after generation.
Maybe I could verify if export backend is HTML and then produce lines:
OPTION specific for HTML
and NOT produce LaTeX related lines
or if LaTeX export
OPTION specific for LaTeX
and NOT produce LaTeX related lines
Would that decision be possible in source block?
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
next prev parent reply other threads:[~2021-03-31 11:18 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
2021-03-31 11:04 ` Jean Louis [this message]
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=YGRXUTvE2RMpxgqz@protected.localdomain \
--to=bugs@gnu.support \
--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).