From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: Including setupfile settings during subtree export (new exporter) Date: Sat, 23 Mar 2013 23:08:54 +0100 Message-ID: <87ppypzs3t.fsf@gmail.com> References: <87obebwj3s.fsf@gmail.com> <87620h27br.fsf@gmail.com> <871ub5264z.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:48004) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UJWca-0005Vz-MI for emacs-orgmode@gnu.org; Sat, 23 Mar 2013 18:09:05 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UJWcY-0003cZ-Lx for emacs-orgmode@gnu.org; Sat, 23 Mar 2013 18:09:04 -0400 Received: from mail-we0-x230.google.com ([2a00:1450:400c:c03::230]:34842) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UJWcY-0003cJ-FT for emacs-orgmode@gnu.org; Sat, 23 Mar 2013 18:09:02 -0400 Received: by mail-we0-f176.google.com with SMTP id s10so1015626wey.21 for ; Sat, 23 Mar 2013 15:09:01 -0700 (PDT) In-Reply-To: (John Hendy's message of "Sat, 23 Mar 2013 16:10:48 -0500") 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@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: John Hendy Cc: emacs-orgmode John Hendy writes: >> At the moment, there's no way to override a #+setupfile: keyword >> locally. > > I guess I don't understand the purpose of #+include, then. It seems we > have only two options: > > 1) #+setupfile: Will apply to entire buffer as well as subtree > exports. Cannot be overridden in subtrees. > > 2) #+include: Applies to entire buffer export only; does nothing for > subtree exports. #+INCLUDE: "file" replaces keyword with "file" contents. During subtree export, replacement will happen if the keyword is located within the subtree being exported. #+SETUPFILE: "file" just reads Org keywords within "file". All Org keywords are global, this one makes no exception. In a nutshell, SETUPFILE should be used for Org set-up. INCLUDE is very general and can be used to build complex documents. The fact that it also copies Org keywords from "file" in the current buffer is merely a side-effect. > What's the preferred way to customize subtrees? Just add #+latex: or > #+latex_header: options inside the subtree? #+LATEX_HEADER: is also global. Use :EXPORT_LATEX_HEADER: in property drawer instead. > Going by the LaTeX export guide > (http://orgmode.org/worg/org-tutorials/org-latex-export.html), I don't > see recommendations for this. As a use case, perhaps I have a subtree > with beamer-compatible markup (each subtree will fit on a slide), but > that I might also include in the whole buffer, or perhaps a different > css file for the whole buffer vs. the subtree. > > Can this be accomplished? Off the top of my head, I think there's no direct way to do it. Though, you can define a property :MY_SETUP: setupfile in the subtree and, within `org-export-before-processing-hook', call a function: - commenting every fSETUPFILE keyword - adding #+SETUPFILE: setupfile at the beginning of the buffer. It involves some (simple) elisp, though. >>> Based on the above, should that line be removed from the Worg update >>> guide? If so, I can do that. >> >> I think so. > > Will do. Thank you. Regards, -- Nicolas Goaziou