From: John Hendy <jw.hendy@gmail.com>
To: Herbert Sitz <hesitz@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: export subtree
Date: Thu, 10 Dec 2015 18:40:32 -0600 [thread overview]
Message-ID: <CA+M2ft87faL=cy8ca+8Hw4D_5XHQwNbfR-zPnxFOtaR6efxptw@mail.gmail.com> (raw)
In-Reply-To: <loom.20151211T012353-628@post.gmane.org>
On Thu, Dec 10, 2015 at 6:27 PM, Herbert Sitz <hesitz@gmail.com> wrote:
> Not a perfect solution, buy I think you can use the #+SELECT_TAGS option to
> set which tress will be exported by default, then tag your desired export
> tree with that tag. Then when you export the full buffer (not just a
> subtree) it will choose the tree with that tag.
>
This was going to be my suggestion as well! In the case that a
majority of the document is desired for export, #+EXCLUDE_TAGS is
helpful as well. For reference:
- http://orgmode.org/manual/Export-settings.html
Export tags are fantastic, as one can add as many as desired and then
simply change the #+select_tags/#+exclude_tags target to generate a
bunch of variations from the same single .org file.
Maybe a little extreme and irrelevant to the OP need(s), but I've also
programmatically generated Org heading syntax with R, spit out
headlines with data driven content, inserted a \newpage at the end of
each, and then split them apart with stapler.[1] I was serving as a
financials secretary for a group at work, managing the budgets of many
chapter entities. This allowed me to start with a .csv with the target
spend for the next year, use R to create a document for each chapter,
and then send the chairs their tailored document vs. manually changing
figures and generating ~40 documents by hand. Worked slick! If any of
that sounds appealing/relevant, let me know and I can share an
example.
Best regards,
John
> E.g.,
> ---------------------------------
> #+SELECT_TAGS: myexporttree
>
> * Main tree :myexporttree:
> fkjaldfk
> ** subhead
> ** subhead
> * anoher heading 1
> * another heading level 1
> ** subhead
> ** subhead
> --------------------------------
>
> In org buffer above it will export only the first subtree now when you
> export the entire buffer. You should be able to export the others
> selectively if you choose scope as 'subtree'. And you can always comment
> out or delete the SELECT_TAGS line if you want to export entire buffer.
>
>
next prev parent reply other threads:[~2015-12-11 0:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 0:27 export subtree Herbert Sitz
2015-12-11 0:40 ` John Hendy [this message]
[not found] ` <CA+iLYJsj=gMvRQXO+h8GKwNvdXzTcZ7vqT_6eYSDnNdbHyJxwg@mail.gmail.com>
2015-12-16 4:43 ` John Hendy
2015-12-11 2:50 ` Skip Collins
2015-12-11 3:53 ` John Hendy
2015-12-11 13:56 ` Skip Collins
-- strict thread matches above, loose matches on Subject: below --
2015-12-10 18:24 Skip Collins
2015-12-10 20:06 ` Andreas Leha
2015-12-10 22:06 ` Skip Collins
2015-12-10 22:43 ` Andreas Leha
2015-12-11 0:10 ` Skip Collins
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
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='CA+M2ft87faL=cy8ca+8Hw4D_5XHQwNbfR-zPnxFOtaR6efxptw@mail.gmail.com' \
--to=jw.hendy@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=hesitz@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).