Hi Scott, (Also adding in the group, just in case anyone else might want to see this; no point typing a message twice!) Took me a little bit to make good on my offer! This was for work, and while it's probably not *that* sensitive (especially with anonymized names), I took the time to change all the links away from our intranet address. Never know who would care about some link between a company and one of its employees on a mailing list... The rest is fairly original to illustrate the use case. I was generating financial "cheat sheets" for the equivalent of college clubs we have at work organized around various technology interests. There's a chair, they're assigned a budget, and need to charge expenses to a particular account number. While all of this information exists in a wiki, our workplace is a bit "old school" and people wanted some type of hard copy. Not being too excited to hand generate 40+ of these I attached a zip of what should be a fairly reproducible example if you have R functionality enabled. If you go the whole document + stapler route to split it, you'll need stapler installed and in your path to run the bash code at the end. There's a link in the document. I forgot that I'd programatically generated an EXPORT_FILE_NAME property for each headline as well. That ended up tying back into Skip's original issue, as I discovered by looking at my generated documents that I went the manual subtree export route. I preferred the headlines as the document title vs. just a headline, and couldn't get there with a bulk export + split. I'd completely forgotten, yet ended up in the same conundrum :) Let me know if you run into issues, and hope you find it helpful! John P.S. I zipped these from within the directory, so you'll want to create a folder and unzip them into it. On Sun, Dec 13, 2015 at 9:25 AM, scot junkin wrote: > This sounds awesome, would enjoy an exampme > > On Dec 10, 2015 5:41 PM, "John Hendy" wrote: >> >> On Thu, Dec 10, 2015 at 6:27 PM, Herbert Sitz 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. >> > >> > >> >