From: Christian Egli <christian.egli@sbs.ch>
To: emacs-orgmode@gnu.org
Subject: Re: [bug] ox-taskjuggler
Date: Mon, 26 Jan 2015 13:30:04 +0100 [thread overview]
Message-ID: <874mrdsp0z.fsf@sbs.ch> (raw)
In-Reply-To: m9tbeb$nfo$1@ger.gmane.org
Søren Mikkelsen <soren@aamikkelsen.dk> writes:
> On 2015-01-23 09:59, Christian Egli wrote:
>> Søren Mikkelsen <soren@aamikkelsen.dk> writes:
>>
>>> It works, but only for tasks that aren't having a start
>>> attribute. It is possible to give a warning if the start
>>> attribute already exists and make the default one, the one
>>> specified in the attributes (drawer)?
>>
>> What exactly doesn't work? Are there two start entries in the task?
>> One because of the SCHEDULED property and one because of the the
>> start property?
>>
>> Then you might have to remove the start property from
>> org-taskjuggler-valid-task-attributes before adding the other
>> valid attributes i.e.
>>
>> ;; Add other valid attributes. (org-taskjuggler--indent-string
>> (org-taskjuggler--build-attributes task
>> org-taskjuggler-valid-task-attributes))
>>
>> Might have to become (untested)
>>
>> ;; Add other valid attributes. (org-taskjuggler--indent-string
>> (org-taskjuggler--build-attributes task (remq 'start
>> org-taskjuggler-valid-task-attributes)))
>>
>> HTH Christian
>>
> The problem by removing the start attribute is that it destroys the
> backward compatibility. I want ox-taskjuggler to accept both methods,
> where the start property attribute overrules the scheduled attribute,
> if this is present.
I don't understand. You get the start of a task using
org-taskjuggler-get-start. This can be either the start attribute or the
SCHEDULED attribute. Then you insert this in the task if it is non-nil.
Since you have dealt with this attribute already you don't need to
handle it in org-taskjuggler--build-attributes. Hence you remove it
(just for this call) from the list of task attributes that need to be
handled.
HTH
Christian
--
Christian Egli
Swiss Library for the Blind, Visually Impaired and Print Disabled
Grubenstrasse 12, CH-8045 Zürich, Switzerland
prev parent reply other threads:[~2015-01-26 12:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-20 12:44 [bug] ox-taskjuggler Søren Mikkelsen
2015-01-20 21:00 ` Nicolas Goaziou
2015-01-21 13:08 ` Søren Mikkelsen
2015-01-21 13:31 ` John Hendy
2015-01-22 7:26 ` Søren Mikkelsen
2015-01-22 10:21 ` Christian Egli
2015-01-22 11:55 ` Søren Mikkelsen
2015-01-23 8:59 ` Christian Egli
2015-01-23 11:31 ` Søren Mikkelsen
2015-01-26 12:30 ` Christian Egli [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874mrdsp0z.fsf@sbs.ch \
--to=christian.egli@sbs.ch \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).