Hi Christian,
Christian Egli writes:
> OK this clears it up. So basically all the patches are fine from my pov.
> Thanks again.
Thanks for confirming.
I'll commit the patches when the FSF papers arrive.
Best,
--
Bastien
Yann Hodique writes:
>> "Christian" == Christian Egli writes:
>> I'm trying to understand the use case here. If I understand correctly
>> the container headline will no longer unconditionally generate a root
>> task. So you could have multiple root tasks? Does this work in both
>> versions
Simon Thum writes:
> Bit I might go at this myself if your patches land, which look excellent
> BTW.
The patches will land as soon as we the copyright assignment is
processed. Chances are that this will be after Org 7.9 though,
but equal chances are that 7.9.1 will closely follow 7.9, so please
On 08/12/2012 10:03 AM, Yann Hodique wrote:
"Christian" == Christian Egli writes:
...
while the new (non-default) one would generate
--8<---cut here---start->8---
project main Main {}
task task1 "Task1" {}
task task2 "Task2" {}
--8<---cut here---
> "Christian" == Christian Egli writes:
> Yann Hodique writes:
>> +(defcustom org-export-taskjuggler-keep-project-as-task t
>> + "Whether to keep the project headline as an umbrella task for
>> + all declared tasks. Setting this to nil will allow maintaining
>> + completely separated task
Yann Hodique writes:
> +(defcustom org-export-taskjuggler-keep-project-as-task t
> + "Whether to keep the project headline as an umbrella task for
> + all declared tasks. Setting this to nil will allow maintaining
> + completely separated task buckets, while still sharing the same
> + resourc
introduce `org-export-taskjuggler-keep-project-as-task' as a flag to toggle
the behavior. Keep old behavior as default.
* org-taskjuggler.el (org-export-taskjuggler-keep-project-as-task): new custom
variable
(org-export-as-taskjuggler): optionally drop the topmost "task" (project)
(org-taskjugg
