From: Kyle Meyer <kyle@kyleam.com>
To: Kisaragi Hiu <mail@kisaragi-hiu.com>, emacs-orgmode@gnu.org
Subject: Re: Format of Effort estimates should be mentioned in its Info node
Date: Sat, 04 Jan 2020 02:55:29 +0000 [thread overview]
Message-ID: <87k168exr2.fsf@kyleam.com> (raw)
In-Reply-To: <Lxbf_R2--3-2@kisaragi-hiu.com>
Kisaragi Hiu <mail@kisaragi-hiu.com> writes:
> Currently, the Info node about effort estimates does not mention what
> format should it be written in. This causes confusion, as a user might
> assume that it's the same format as schedulers (10m, 6h, etc.) like I
> did.
>
> Simply mentioning "Effort estimates need to have the format H:MM"
I don't personally use effort estimates, but quickly poking around I see
some indication that estimates should work fine with things like 10min
rather than 0:10. In particular org-set-effort has a bit that looks
like this:
(org-refresh-property '((effort . identity)
(effort-minutes . org-duration-to-minutes))
value)
The presence of org-duration-to-minutes hints to some sort of
normalization:
(org-duration-to-minutes "10min") ; => 10.0
(org-duration-to-minutes "0:10") ; => 10.0
And it looks like org-agenda-compare-effort uses the effort-minutes text
property. That's presumably why, when I view the entries below in the
agenda, org-agenda-filter-by-effort (bound to "_") treats them the same:
* TODO a
:PROPERTIES:
:Effort: 10min
:END:
* TODO b
:PROPERTIES:
:Effort: 0:10
:END:
But that's just one use of effort values, and it sounds like you've hit
into cases where the 10min form didn't work as expected. Could you
provide more details?
> (copied from the docstring or org-effort-property, the only*
> description of the format I could find) in the Info node would be
> enough.
Given the above, it seems like org-effort-property's docstring is at
least somewhat inaccurate.
next prev parent reply other threads:[~2020-01-04 2:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-02 19:14 Format of Effort estimates should be mentioned in its Info node Kisaragi Hiu
2020-01-04 2:55 ` Kyle Meyer [this message]
2020-01-04 5:20 ` Kisaragi Hiu
2020-01-04 5:29 ` Jean-Christophe Helary
2020-01-07 8:41 ` Nicolas Goaziou
2020-01-31 11:13 ` Bastien
2020-02-01 9:24 ` Bastien
2020-02-01 16:40 ` Kisaragi Hiu
2020-02-01 16:45 ` Bastien
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=87k168exr2.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@kisaragi-hiu.com \
/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).