From: John Hendy <jw.hendy@gmail.com>
To: John Hendy <jw.hendy@gmail.com>, emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Bug: ox-taskjuggler :effort: property incorrectly converted when in minutes
Date: Sun, 2 Nov 2014 17:07:17 -0600 [thread overview]
Message-ID: <CA+M2ft93PHYYHHF+sby2cb5+g1gv=jBmbNP1NpkwAnRvx7LqCw@mail.gmail.com> (raw)
In-Reply-To: <87zjc9fbq6.fsf@nicolasgoaziou.fr>
On Sun, Nov 2, 2014 at 5:01 PM, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
> John Hendy <jw.hendy@gmail.com> writes:
>
>> That mostly makes sense. Org's not case-sensitive, correct?
>
> Correct.
>
>> I was looking at the [granted, outdated] taskjuggler documentation and
>> it features estimates in days (i.e. 10d): -
>> http://orgmode.org/worg/org-tutorials/org-taskjuggler.html
>>
>> Is this recent (as in post-writing of that worg page)?
>
> I cannot remember.
>
>> Or are there other formats that could be accepted?
>
> Not at the moment, since ox-taskjuggler.el hardcodes
>
> (org-duration-string-to-minutes effort)
>
>> It's unfortunate that org and taskjuggler overlap on this, as ideally
>> one could pass any tj attribute as a property and it'd "do the right
>> thing." I see why the issue exists now.
>>
>> So if I want to estimate a task taking 10 days, I need to input 80:00?
>
> For now yes.
>
> The code could be improved, however. I.e, if effort matches
>
> "\\`[0-9]+:[0-5][0-9]\\'"
>
> use `org-duration-string-to-minutes', otherwise insert it as-is.
Thanks for the explanation. I pretty much only use duration, which has
never had an issue. As a fluke I used effort and noticed the big
difference. Thanks for illuminating the situation!
John
>
>
> Regards,
next prev parent reply other threads:[~2014-11-02 23:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-02 22:26 Bug: ox-taskjuggler :effort: property incorrectly converted when in minutes John Hendy
2014-11-02 22:47 ` Nicolas Goaziou
2014-11-02 22:54 ` John Hendy
2014-11-02 23:01 ` Nicolas Goaziou
2014-11-02 23:07 ` John Hendy [this message]
2014-11-02 23:25 ` Nicolas Goaziou
2014-11-03 21:53 ` John Hendy
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='CA+M2ft93PHYYHHF+sby2cb5+g1gv=jBmbNP1NpkwAnRvx7LqCw@mail.gmail.com' \
--to=jw.hendy@gmail.com \
--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).