Re: [O] New Exporter BUG/Change in behaviour

2013-04-06 Thread Thorsten Jolitz
Nicolas Goaziou writes: > Thorsten Jolitz writes: > >> Nicolas Goaziou writes: >> >>> No. The "d:" item only applies to regular drawers. >>> >>> `property-drawer' elements are not among them. Back-ends handle these >>> beasts as they see fit (they usually ignore them, as you can tell). >> >> I

Re: [O] New Exporter BUG/Change in behaviour

2013-04-06 Thread Nicolas Goaziou
Thorsten Jolitz writes: > Nicolas Goaziou writes: > >> No. The "d:" item only applies to regular drawers. >> >> `property-drawer' elements are not among them. Back-ends handle these >> beasts as they see fit (they usually ignore them, as you can tell). > > I actually have a use-case where I woul

Re: [O] New Exporter BUG/Change in behaviour

2013-04-06 Thread Thorsten Jolitz
Nicolas Goaziou writes: > No. The "d:" item only applies to regular drawers. > > `property-drawer' elements are not among them. Back-ends handle these > beasts as they see fit (they usually ignore them, as you can tell). I actually have a use-case where I would like to export the property-drawer

Re: [O] New Exporter BUG/Change in behaviour

2013-04-06 Thread Nicolas Goaziou
Hello, Thorsten Jolitz writes: > Shouldn't the > > ,- > | :EXPORT_OPTIONS: d:t > `- > > setting in the following minimal org-file export the property-drawer for > this subtree too? > > ,--- > | * header1 > | :PROPERTIES: > | :EXPORT

Re: [O] New Exporter BUG/Change in behaviour

2013-04-06 Thread Thorsten Jolitz
Nicolas Goaziou writes: Hello, > The new exporter distinguishes between subtree export (toggled with C-s > key within the dispatcher) and region export. In the old exporter, C-c @ > + export command would give you a subtree export. This is not the case > in the new exporter. You have to explicit

Re: [O] New Exporter BUG/Change in behaviour

2013-04-05 Thread Bernt Hansen
Nicolas Goaziou writes: > Hello, > > Bernt Hansen writes: > >> Is this a bug? > > No, it isn't. > >> My current workaround is to delete the global #+OPTIONS >> line (but that doesn't feel right since I have to add it back to export >> what is left to do for the entire file when sharing it with o

Re: [O] New Exporter BUG/Change in behaviour

2013-04-05 Thread Nicolas Goaziou
Hello, Bernt Hansen writes: > My org file has > > #+OPTIONS: tasks:todo > > This globally skips DONE tasks in my exports when I export the entire > file in both the old and new exporter. > > If I select a task with C-c @ that is DONE (or any done state) and try > to export that in the new export

[O] New Exporter BUG/Change in behaviour

2013-04-05 Thread Bernt Hansen
Hi Nicolas, I finally updated to the latest master branch at work yesterday to move to the new exporter and found the following change I don't know how to deal with. My org file has #+OPTIONS: tasks:todo This globally skips DONE tasks in my exports when I export the entire file in both the old