Thanks Jambunathan K. Your concise summary is correct.
As it stands, selective export from Orgmode is already excellent --
combining both #+EXPORT_SELECT_TAGS: and #+EXPORT_EXCLUDE_TAGS: in various
ways allows for very precise exporting; this is particularly apparent when
dealing with tags at diff
IIUC, what you are saying is that you would like to define few atomic
tags and a few composite tag. A composite tag is presumably a union of
some of those atomic tags. You need an ability to selectively export of
the items that fall under the composite tag.
Orgmode allows selective viewing (and e
John Tait writes:
> Thanks for that. But then what are #-FILETAGS for?
>
FILETAGS are primarily used in the agenda -- i.e., filetags are
inherited by the entire file, so when you filter the agenda by tags, the
filetags are also considered.
Not much work has been done to integrate filetags with
> May I propose an additional feature?
> We could assign tags to hierarchies of other tags.
As a technical editor how do you think you would make use of
hierarchical tags. Without getting in to how this feature might be
implemented, if you can articulate your particular requirements and your
par
John Tait writes:
>
> While I am here (sorry), I couldn't get #+FILETAGS: to work in org-version
> 7.4.
>
> For example, if I export a file (to html) File1.org with
> "#+EXPORT_EXCLUDE_TAGS: john", and then I include File2.org, I can see
> File2.org included as part the export of File1 as expecte
