From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kisaragi Hiu Subject: Re: Format of Effort estimates should be mentioned in its Info node Date: Sat, 4 Jan 2020 06:20:27 +0100 (CET) Message-ID: References: <87k168exr2.fsf@kyleam.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:44185) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1inbrT-0005tB-FI for emacs-orgmode@gnu.org; Sat, 04 Jan 2020 00:20:33 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1inbrS-0007CT-67 for emacs-orgmode@gnu.org; Sat, 04 Jan 2020 00:20:31 -0500 Received: from w4.tutanota.de ([81.3.6.165]:46658) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1inbrR-00077l-Vc for emacs-orgmode@gnu.org; Sat, 04 Jan 2020 00:20:30 -0500 In-Reply-To: <87k168exr2.fsf@kyleam.com> 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: Kyle Meyer , Emacs Orgmode It didn't work for me because I gave it "10m" which actually means 10 month= s, I've realized. Still, Durations as defined by org-duration.el should be described in the m= anual like how Timestamps are. 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: > Kisaragi Hiu 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") ; =3D> 10.0 > (org-duration-to-minutes "0:10") ; =3D> 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. >