On Thu, Dec 10, 2015 at 6:27 PM, Herbert Sitz <hes...@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. > >
