From: "Søren Mikkelsen" <soren@aamikkelsen.dk>
To: emacs-orgmode@gnu.org
Subject: Re: [bug] ox-taskjuggler
Date: Fri, 23 Jan 2015 12:31:23 +0100 [thread overview]
Message-ID: <m9tbeb$nfo$1@ger.gmane.org> (raw)
In-Reply-To: <878ugtswhg.fsf@sbs.ch>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
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.
- --
Best regards,
Søren Mikkelsen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJUwjEEAAoJECUE7rt2jWDw5WQH/AhkKBjfWZLryYG+Zqj1D5Re
+JXahe52HYf5oBXeSJHF250wKxF4KSme6JXHBfO5lfT5IZY+YwZTeUxm0a2KXod3
y9bxrWKqNglkqLLHxpwsZMpTGfcy4LOGJwxqL+brcRSJzftf17bpKnD1pcj62/uT
UxLQlWbmmj0WqP4f0xLMtyvkRc5OWDz6T/mylxM0/26cK2xIhdigV42dTXvwFu13
NZdfhL5lUgORHOYseSfV23e/89pnw3V9PIO/4QA/6HEBP7icsSlMb4qiAOMf6wdE
JbPVf4hkYfDmBKcFuWeWKAdz94I/Xcov2/0XoCc/qOFEhhlAvxrFm+KzI/Xjr30=
=EpK7
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2015-01-23 11:31 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 [this message]
2015-01-26 12:30 ` Christian Egli
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='m9tbeb$nfo$1@ger.gmane.org' \
--to=soren@aamikkelsen.dk \
--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).