John Hendy wrote: > Thinking about it more, using select_tags as a potential solution to > your export of a subtree without navigating to it, problems could > arise if more than one were tagged. If multiple same-level headlines > were tagged with the select_tag, which one should Org use as the > "master" for the document title/level structure?
Nevertheless, I like the idea of a special tag to designate the top level export. Call it :master:. The first headline with the tag :master: would cause export actions to default to that subtree. That way one would be able to edit deep inside the master subtree or outside of it and still easily and consistently generate the correct document. It would also help with exporting from emacs/org in batch mode without a user to put point at the correct subtree location. > It sounds like the C-u option did work for you, correct? Correct. C-u works and I have what I need for now. What I ended up doing is placing the contents of the export tree into an INCLUDE file. I duplicate all of the export header options in that file. So my workflow is simply to edit that document and process it for export without using the subtree option from the parent. It does break the convenience of keeping everything together in one file.
