From: John Hendy <firstname.lastname@example.org>
To: Nicolas Goaziou <email@example.com>
Cc: emacs-orgmode <firstname.lastname@example.org>
Subject: Re: Including setupfile settings during subtree export (new exporter)
Date: Sat, 23 Mar 2013 16:10:48 -0500 [thread overview]
Message-ID: <CA+M2ft_So7a64HMbHhZ45FsAY1E82vd3NtetDtCnPmaG559Stg@mail.gmail.com> (raw)
On Sat, Mar 23, 2013 at 3:49 PM, Nicolas Goaziou <email@example.com> wrote:
> John Hendy <firstname.lastname@example.org> writes:
>> Thanks for the clarification. For me (since I'm not an elisper), the
>> mechanics aren't too important. All I really want is the correct way
>> to apply org-mode settings to a buffer or a subtree by default, unless
>> I specify otherwise inside a subtree to override the buffer-wide
> At the moment, there's no way to override a #+setupfile: keyword
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
What's the preferred way to customize subtrees? Just add #+latex: or
#+latex_header: options inside the subtree? 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?
>> Based on the above, should that line be removed from the Worg update
>> guide? If so, I can do that.
> I think so.
>> I'll change back to #+setupfile!
> Note that LaTeX packages added through SETUPFILE can also be found
> during latex fragments previewing, which isn't true for INCLUDE
> Nicolas Goaziou
next prev parent reply other threads:[~2013-03-23 21:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-22 15:19 Including setupfile settings during subtree export (new exporter) John Hendy
2013-03-22 15:27 ` Nicolas Goaziou
2013-03-22 17:12 ` John Hendy
2013-03-23 20:24 ` Nicolas Goaziou
2013-03-23 20:37 ` John Hendy
2013-03-23 20:49 ` Nicolas Goaziou
2013-03-23 21:10 ` John Hendy [this message]
2013-03-23 22:08 ` Nicolas Goaziou
2013-03-23 22:18 ` John Hendy
2013-03-23 22:37 ` Nicolas Goaziou
2013-03-24 12:13 ` Mike McLean
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 \
* 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).