all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: emacs-orgmode@gnu.org
Subject: Re: order of evaluation upon export: macros are evaluated too soon
Date: Thu, 08 Jun 2017 12:43:46 +0100	[thread overview]
Message-ID: <87poeen1ql.fsf@delle7240.chemeng.ucl.ac.uk> (raw)
In-Reply-To: <e995e3bb8ecb466ba85e8be925f1a72b@HE1PR01MB1898.eurprd01.prod.exchangelabs.com> (Nicolas Goaziou's message of "Wed, 7 Jun 2017 19:56:58 +0000")

[-- Attachment #1: Type: text/plain, Size: 645 bytes --]

On Wednesday,  7 Jun 2017 at 19:56, Nicolas Goaziou wrote:

[...]

> What about simply removing macros in :noexport: trees from
> a pre-processing-hook?

Hi Nicolas,

Thanks for the suggestion.  It makes sense but the problem (for me) is
the "simply" in the above. ;-)

But Charles's solution works perfectly so I'm happy!

I do wonder, philosophically, about the use cases for macro expansion
and the resulting implementation.  My understanding is that macros are
only for export so should they not pay attention to export exclusion
directives?

Thanks again,
eric

-- 
: Eric S Fraga (0xFFFCF67D), Emacs 26.0.50, Org release_9.0.7-531-g530113

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 194 bytes --]

  parent reply	other threads:[~2017-06-08 11:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-07 15:47 order of evaluation upon export: macros are evaluated too soon Eric S Fraga
2017-06-07 18:43 ` Charles C. Berry
2017-06-07 19:56   ` Nicolas Goaziou
     [not found]   ` <e995e3bb8ecb466ba85e8be925f1a72b@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-06-08 11:43     ` Eric S Fraga [this message]
2017-06-08 12:36       ` Nicolas Goaziou
     [not found]       ` <62ad9bab51254374aaa68b4ef0fd0b29@DB5PR01MB1895.eurprd01.prod.exchangelabs.com>
2017-06-10 10:44         ` Eric S Fraga
     [not found] ` <51249f80b2dc43118f5855b8d0ce737e@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-06-08 11:39   ` Eric S Fraga

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87poeen1ql.fsf@delle7240.chemeng.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.