From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Sebastien Vauban" Subject: Re: Bug: New Exporter macro expansion Date: Wed, 10 Oct 2012 21:10:34 +0200 Message-ID: <80zk3u6t3p.fsf@somewhere.org> References: <87txu86lts.fsf@gmail.com> <80r4pcugl2.fsf@somewhere.org> <87mx006j9f.fsf@gmail.com> <87ehl65yhi.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org To: emacs-orgmode-mXXj517/zsQ@public.gmane.org Nicolas and Jonathan, Nicolas Goaziou wrote: > Jonathan Leech-Pepin 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 part. Are there constraints on what we can include via which mechanism? Best regards, Seb -- Sebastien Vauban