On May 9, 2014 11:32 PM, "Nick Dokos" <ndokos@gmail.com> wrote:
>
> John Hendy <jw.hendy@gmail.com> writes:
>
> > In creating a packing/buy list for an upcoming camping trip, I wanted
> > two exports:
> > - one for things to buy
> > - one for everything on the list for packing
> >
> > My strategy was to tag things to buy with :export: (perhaps foolish,
> > but it was the obvious choice to selectively export them) to create my
> > shopping list. I'd also like an alternate export with all headlines in
> > the subtree exported.
> >
> > Now the list is done like that, but I'm not sure how to export
> > everything without undoing all the tags on the buy list items.
> >
> > I'm thinking I should have done something like a :buy: tag, then set
> > SELECT_TAGS to target those items, followed by removing that export
> > option and exporting as normal to get them all. Just thought I'd see
> > if there was a way to override the function of :export: as it
> > typically behaves.
> >
> >
>
> An empty SELECT_TAGS selects everything I believe:
>
> --8<---------------cut here---------------start------------->8---
> #+SELECT_TAGS:
>
> * a
                                         :export:
>
> * b
>
> * c
>
> * d
                                         :export:
> --8<---------------cut here---------------end--------------->8---
>
> Then you can comment it out to get just the :export:ed headlines.
> But a semantically meaningful tag seems better to me.
>

Awesome, and I'll keep that in mind. Agreed re. the better strategy with
non-org tags, which is what I ended up doing.

Thanks!
John

> --
> Nick
>
>