I don't know if the following will help, but here goes: you are not limited to export/noexport
tags in order to trigger the selective exporting functionality.
E.g. suppose that you want to share some sections with everybody, some sections with Tom, some sections with Dick and some sections with Harry (and it might happen that some of these sections overlap). You tag each section with a tag corresponding to the person you want to share that section with; if a section is to be shared with multiple people, you tag it with all relevant tags; if a section is to be shared with everybody you tag it with e.g. the tag common
[1]. Here's a concrete example:
* zero :common:
* one :tom:
* two :dick:
* three :harry:
* four :tom:dick:
* five :tom:harry:
* six :dick:harry:
So sections zero
, one
, four
and five
are to be shared with Tom, sections zero
, two
, four
and six
are to be shared with Dick and sections zero
, three
, five
and six
are to be shared with Harry.
You can use #+SELECT_TAGS
(which by default contains only the export
tag) to define which tags you want to select for export. E.g to select only the common sections that are tagged common
and the sections tagged tom
, add this line to the top of the file before exporting:
#+SELECT_TAGS: common tom
...
You only have to change that one line in order to change the export to select Dick's sections or Harry's sections. If you add another person to the list, all you have to do is add the tag for the new person to the tags of each section that the new person should see[2].
I don't know if this will cover all your needs, but it seems to cover the situation you describe in your comment above; it can also easily cover the selective export you describe in your question: tag each section with a different tag and then add to #+SELECT_TAGS
only the tags for the sections you want to export.
There is also #+EXCLUDE_TAGS
(which contains just noexport
by default) that could potentially be used in more complicated situations, but you should keep things as simple as possible: using both might become confusing.
See Export Settings in the manual for more details (although I think the description leaves something to be desired).
Footnotes:
[1] You could tag it with all the person tags instead, but it's better to have a tag like common
for this case.
[2] If you tagged the common sections with the tags for each person, you'd have to change each such section's tags and add the new person to all of them. That's why it's better to use a common
tag.
marks
are you talking about? E.gC-<space>
sets themark
at one end of a region (andpoint
is the other end). But there is only one such at at any particular time, so how are you going to use that for multiple regions? Or perhaps you are talking aboutbookmarks
?