On 2014-05-10 05:11 John Hendy wrote:
> Hello,
>
>
> 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
If those two lists are disjoint, you can put each of them under its own
subtree and exp
On May 10, 2014 4:03 AM, "Alexander Baier"
wrote:
>
> On 2014-05-10 05:11 John Hendy wrote:
> > Hello,
> >
> >
> > 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
>
> If those two li
On May 9, 2014 11:32 PM, "Nick Dokos" wrote:
>
> John Hendy 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:
On 2014-05-10 05:11 John Hendy wrote:
> 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
If these two lists are disjoint you could put each of them under its own
subtree and export these su
John Hendy 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 selectivel
Hello,
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
