From: Bruno BEAUFILS <email@example.com>
To: Tim Cross <firstname.lastname@example.org>
Cc: Bruno BEAUFILS <email@example.com>, firstname.lastname@example.org
Subject: Re: looking for a macro eval workaround (9.1 vs 9.2 and +) for export backend test
Date: Sun, 22 Nov 2020 21:49:15 +0100 [thread overview]
Message-ID: <email@example.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 743 bytes --]
On Sun, Nov 22, 2020 at 12:18:07AM +1100, Tim Cross wrote:
> Hmm, I just use backend specific blocks for this purpose. e.g.
> #+begin_export latex
Yes but it is what I try to avoid in order to let the file as simple
and readable as possible.
> IMO the org #+MACRO is really just a text substitution mechanism (like
> C), not a 'real' macro (like elisp has) and as is the case with C, you
> really need to keep them pretty simple. Once you start using them to
> evaluate code, it isn't hard to find yourself in a mine field.
I agree but as the possibility was offered I used it ;-)
The only trouble is that this eval feature changed in a hard way
between 9.1 and 9.2.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-11-22 20:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-21 10:56 looking for a macro eval workaround (9.1 vs 9.2 and +) for export backend test Bruno BEAUFILS
2020-11-21 13:18 ` Tim Cross
2020-11-22 20:49 ` Bruno BEAUFILS [this message]
2020-11-23 10:19 ` Eric S Fraga
2020-11-23 13:02 ` Bruno BEAUFILS
2020-11-23 13:12 ` Eric S Fraga
2020-11-29 17:30 ` Bruno BEAUFILS
2020-11-29 17:45 ` Eric S Fraga
2020-11-29 20:55 ` Tom Gillespie
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).