From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jean-Christophe Helary Subject: Re: Format of Effort estimates should be mentioned in its Info node Date: Sat, 4 Jan 2020 14:29:52 +0900 Message-ID: References: <87k168exr2.fsf@kyleam.com> Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.40.2.2.4\)) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:54891) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1inc0j-0000yd-Nx for emacs-orgmode@gnu.org; Sat, 04 Jan 2020 00:30:06 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1inc0i-00064Z-2U for emacs-orgmode@gnu.org; Sat, 04 Jan 2020 00:30:05 -0500 Received: from relay6-d.mail.gandi.net ([217.70.183.198]:45751) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1inc0h-0005z2-Sj for emacs-orgmode@gnu.org; Sat, 04 Jan 2020 00:30:04 -0500 Received: from [172.20.10.2] (KD182251137124.au-net.ne.jp [182.251.137.124]) (Authenticated sender: jean.christophe.helary@traduction-libre.org) by relay6-d.mail.gandi.net (Postfix) with ESMTPSA id 5790BC0002 for ; Sat, 4 Jan 2020 05:29:57 +0000 (UTC) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Emacs Orgmode > On Jan 4, 2020, at 14:20, Kisaragi Hiu wrote: >=20 > It didn't work for me because I gave it "10m" which actually means 10 = months, I've realized. >=20 > Still, Durations as defined by org-duration.el should be described in = the manual like how Timestamps are. This does look like a potential contribution to the package. Jean-Christophe Helary >=20 > 2020=E5=B9=B41=E6=9C=884=E6=97=A5 11:55 =E5=B7=AE=E5=87=BA=E3=81=97=E4=BA= =BA=EF=BC=9A kyle@kyleam.com: >=20 >> Kisaragi Hiu writes: >>=20 >>> 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. >>>=20 >>> Simply mentioning "Effort estimates need to have the format H:MM" >>>=20 >>=20 >> 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: >>=20 >> (org-refresh-property '((effort . identity) >> (effort-minutes . org-duration-to-minutes)) >> value) >>=20 >> The presence of org-duration-to-minutes hints to some sort of >> normalization: >>=20 >> (org-duration-to-minutes "10min") ; =3D> 10.0 >> (org-duration-to-minutes "0:10") ; =3D> 10.0 >>=20 >> 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: >>=20 >> * TODO a >> :PROPERTIES: >> :Effort: 10min >> :END: >>=20 >> * TODO b >> :PROPERTIES: >> :Effort: 0:10 >> :END: >>=20 >> 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? >>=20 >>> (copied from the docstring or org-effort-property, the only* >>> description of the format I could find) in the Info node would be >>> enough. >>>=20 >>=20 >> Given the above, it seems like org-effort-property's docstring is at >> least somewhat inaccurate. >>=20 >=20 >=20 Jean-Christophe Helary ----------------------------------------------- http://mac4translators.blogspot.com @brandelune