emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Bug: New Exporter macro expansion
Date: Wed, 10 Oct 2012 21:10:34 +0200	[thread overview]
Message-ID: <80zk3u6t3p.fsf@somewhere.org> (raw)
In-Reply-To: 87ehl65yhi.fsf@gmail.com

Nicolas and Jonathan,

Nicolas Goaziou wrote:
> Jonathan Leech-Pepin <jonathan.leechpepin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>> I do however have one other issue that I seem to recall working in the previous
>> exporter.
>> 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?
> Not really intended. That's because include keywords expansion was
> happening after macro expansion (see `org-export-as').

Shouldn't macros be included via SETUPFILE?  I've always considered that
INCLUDE was for the (sort of) text part, while SETUPFILE for the keywords

Are there constraints on what we can include via which mechanism?

Best regards,

Sebastien Vauban

  reply	other threads:[~2012-10-10 19:10 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
2012-10-10 11:59         ` Nicolas Goaziou
2012-10-10 19:10           ` Sebastien Vauban [this message]
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=80zk3u6t3p.fsf@somewhere.org \
    --to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.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).