emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jonathan Leech-Pepin <jonathan.leechpepin@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org,
	Sebastien Vauban
Subject: Re: Bug: New Exporter macro expansion
Date: Tue, 9 Oct 2012 10:53:52 -0400	[thread overview]
Message-ID: <CAEWDx5fg5XMfZZ1JyJR1=QdKk2PxHSN+YF=_rVMvmfSLsF706Q@mail.gmail.com> (raw)
In-Reply-To: <87mx006j9f.fsf@gmail.com>


On 6 October 2012 05:29, Nicolas Goaziou <n.goaziou@gmail.com> wrote:
> Hello,
> "Sebastien Vauban"
> <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:
>> Did you go further in the thinking about what the macros will support in the
>> future?  Such as: multiline macros, recursive macros, Babel blocks,
>> etc.
> Macro expansion is already recursive.
> I think multiline macros are not needed, as they would be redundant with
> Babel. Despite what is written (for now) in the documentation, macros
> should be used for simple replacements, and Babel machinery for
> everything else.
> Though, you can have a macro expand to a one-line Babel call if you want
> to.

Thank you for the fix.

I do however have one other issue that I seem to recall working in the previous

If I use #+INCLUDE: "./macros.org" to store a list of common macros for
several files they will not appear in the exported document.  Is this intended?

> Regards,
> --
> Nicolas Goaziou



  reply	other threads:[~2012-10-09 14:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-04 19:44 Bug: New Exporter macro expansion Jonathan Leech-Pepin
2012-10-06  8:34 ` Nicolas Goaziou
2012-10-06  8:53   ` Sebastien Vauban
2012-10-06  9:29     ` Nicolas Goaziou
2012-10-09 14:53       ` Jonathan Leech-Pepin [this message]
2012-10-10 11:59         ` Nicolas Goaziou
2012-10-10 19:10           ` Sebastien Vauban
2012-10-10 20:38             ` Nicolas Goaziou

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:

  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='CAEWDx5fg5XMfZZ1JyJR1=QdKk2PxHSN+YF=_rVMvmfSLsF706Q@mail.gmail.com' \
    --to=jonathan.leechpepin@gmail.com \
    --cc=n.goaziou@gmail.com \
    --cc=public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org \
    --cc=public-wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@plane.gmane.org \


* 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).