Rasmus writes:
> Kosyrev Serge <_deepf...@feelingofgreen.ru> writes:
>> +(defun org-taskjuggler-multivalued-property (property element)
>> + "Obtain PROPERTY of ELEMENT, treating it as a multi-valued property.
>
> Isn't the docstring a bit tautological?
Aaron Ecay writes:
> 2015ko azaroak 8an, Kosyrev Serge-ek idatzi zuen:
>>
>> * ox-taskjuggler.el (org-taskjuggler--build-task): fix priority
>> specification
>> by allowing it to be directly passed down, in case it parses as an integer.
>> ---
>&g
Aaron Ecay writes:
> Hi Kosyrev,
>> @@ -301,7 +301,7 @@ but before any resource and task declarations."
>>:type '(string :tag "Preamble"))
>>
>> (defcustom org-taskjuggler-valid-task-attributes
>
> Is this an open-ended list that an average user could meaningfully add
> to? If not, perhaps
* ox-taskjuggler.el (org-taskjuggler-trim-ids-from-titles): new custom
(org-taskjuggler--build-task): trim task ids from titles, when the new
custom variable asks for this (enabled by default).
---
contrib/lisp/ox-taskjuggler.el | 18 +++---
1 file changed, 15 insertions(+), 3 deletio
* ox-taskjuggler.el (org-taskjuggler--build-task): fix priority specification
by allowing it to be directly passed down, in case it parses as an integer.
---
contrib/lisp/ox-taskjuggler.el | 12 +---
1 file changed, 9 insertions(+), 3 deletions(-)
diff --git a/contrib/lisp/ox-taskjuggle
* ox-taskjuggler.el (org-taskjuggler--build-task): fix priority specification
by allowing it to be directly passed down, in case it parses as an integer.
---
contrib/lisp/ox-taskjuggler.el | 12 +---
1 file changed, 9 insertions(+), 3 deletions(-)
diff --git a/contrib/lisp/ox-taskjuggle
* ox-taskjuggler.el (org-taskjuggler--build-project): Allow the project
end and duration to be specified via properties of the root node.
---
contrib/lisp/ox-taskjuggler.el | 9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/contrib/lisp/ox-taskjuggler.el b/contrib/lisp/o
* ox-taskjuggler.el (org-taskjuggler-map-special-nodes):
new function to capture mapping over tagged special nodes.
(org-taskjuggler-project-plan): factor to use the new function.
---
contrib/lisp/ox-taskjuggler.el | 17 ++---
1 file changed, 10 insertions(+), 7 deletions(-)
diff --g
* ox-taskjuggler.el (org-taskjuggler-valid-resource-attributes): add leaves
to the list of valid resource attributes
---
contrib/lisp/ox-taskjuggler.el | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/contrib/lisp/ox-taskjuggler.el b/contrib/lisp/ox-taskjuggler.el
index cfb28f2
* ox-taskjuggler.el (org-taskjuggler-multivalued-property): new function
to operate on multivalued properties.
---
contrib/lisp/ox-taskjuggler.el | 10 ++
1 file changed, 10 insertions(+)
diff --git a/contrib/lisp/ox-taskjuggler.el b/contrib/lisp/ox-taskjuggler.el
index 82aaa7e..8036af3
* ox-taskjuggler.el (org-taskjuggler-valid-task-attributes): add depends
to the list of valid task attributes
---
contrib/lisp/ox-taskjuggler.el | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/contrib/lisp/ox-taskjuggler.el b/contrib/lisp/ox-taskjuggler.el
index 2bd47e6..cfb28
* ox-taskjuggler.el (org-taskjuggler--build-task): interpret 'allocate'
as a multivalued property, to pave the way for future completion-enabled
entry of this property.
---
contrib/lisp/ox-taskjuggler.el | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/contrib/lisp/ox-ta
* ox-taskjuggler.el (org-taskjuggler-project-plan): allow for include
directives to be inserted after resource and task sections.
---
contrib/lisp/ox-taskjuggler.el | 48 ++
1 file changed, 34 insertions(+), 14 deletions(-)
diff --git a/contrib/lisp/ox-task
Good evening, folks!
This is a bunch of solutions for the most direct obstacles that
I encountered, mostly additions of direct Org-property -> TJ-attribute
export pathways.
Kosyrev Serge (8):
ox-taskjuggler.el: allow direct 'leaves' specification
ox-taskjuggler.el: factor
Hi,
Rasmus writes:
> Kosyrev Serge <_deepf...@feelingofgreen.ru> writes:
>> The question is.. the only documentation for ox-taskjuggler that exists
>> in Worg, seems to only cover the surface aspects of export -- none of
>> the existing documentation touches on the mu
Rasmus writes:
> Serge Kosyrev <_deepf...@feelingofgreen.ru> writes:
>> I'm not sure how wise it would be to raise barriers for contribution,
>> given the current state of the thing..
>
> I don't know what state you refer to.
Well, I couldn't use it, without significant tweaking.
It feels as if
Good day folks!
I have tried to use ox-taskjuggler and faced what appeared to be a
mountain of.. infelicities and semi-broken functionality.
A need shapes the man, so I plowed through the most direct obstacles,
and finally managed to get what I want from the beast -- mostly by
adding direct Org-p
17 matches
Mail list logo