From: John Hendy <email@example.com>
To: Nicolas Goaziou <firstname.lastname@example.org>
Cc: emacs-orgmode <email@example.com>
Subject: Re: Including setupfile settings during subtree export (new exporter)
Date: Sat, 23 Mar 2013 17:18:28 -0500 [thread overview]
Message-ID: <CA+M2ft81xHnY8uQ5obwR+T+vm0yz8u3tbJYcvHXMyKPCZPfYYw@mail.gmail.com> (raw)
On Sat, Mar 23, 2013 at 5:08 PM, Nicolas Goaziou <firstname.lastname@example.org> wrote:
> John Hendy <email@example.com> writes:
>>> 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
>> 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.
Got it... I think :) Perhaps the Worg page should clarify this, as it
does, then, seem like #+include is the best practice for LaTeX options
and #+setupfile is just supposed to be for TODO settings? I say this
as my googling for "Org keywords org-mode" yields this:
Is that the meaning of "Org keywords" (just TODO keyword/work flow
settings)? Or would you also include #+options in that group?
> 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.
Good to know. I was unaware of that. Is there a list of these? The
only one I've run across is the new Beamer export Worg page:
That's a great table and it would be great to have that for all
properties. Or perhaps this page could link to that comprehensive list
if it exists, or let the user know how to find it:
>> 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.
I'll consider that. My setups aren't typically so complicated to
probably require something like this. Out of curiosity, would
#+include in the header of the file be overridden by #+include in the
subtree? If not, it could be as simple as having a temporary include
file that I'd modify prior to subtree export and then just comment out
the main buffer #+include prior to exporting.
>>>> 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.
> Nicolas Goaziou
Thanks again for the clarification. I do hope I can repay those doing
work on actual code (where I lack the abilities) by getting some of
these gems out of the mailing list and into Worg for the community.
next prev parent reply other threads:[~2013-03-23 22:18 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
2013-03-23 22:08 ` Nicolas Goaziou
2013-03-23 22:18 ` John Hendy [this message]
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).