From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: [bug?] Computations on efforts expressed in days Date: Tue, 01 May 2012 18:02:13 +0200 Message-ID: <87aa1rkhyy.fsf@gnu.org> References: <80ipgy77d4.fsf@somewhere.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:59500) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SPFW1-0006iw-G2 for emacs-orgmode@gnu.org; Tue, 01 May 2012 12:01:26 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SPFVz-0004AW-OS for emacs-orgmode@gnu.org; Tue, 01 May 2012 12:01:24 -0400 Received: from plane.gmane.org ([80.91.229.3]:39352) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SPFVz-0004AB-Bs for emacs-orgmode@gnu.org; Tue, 01 May 2012 12:01:23 -0400 Received: from public by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1SPFVw-0005EV-Us for emacs-orgmode@gnu.org; Tue, 01 May 2012 18:01:20 +0200 In-Reply-To: <80ipgy77d4.fsf@somewhere.org> (Sebastien Vauban's message of "Tue, 17 Apr 2012 16:36:39 +0200") 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-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Sebastien Vauban Cc: public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org "Sebastien Vauban" writes: > I want to compute efforts given in days. As explained by the doc of > `org-effort-durations', we must add a =d= modifier to tell Org that given numbers > must be multiplied by 480 (in the case of hours) to get the correct number of > corresponding minutes. > > I did that, but (as shown in the following inlined ECM): > > - the computed total for task A is interpreted as hours (4.5 days becomes > 4 hours 30 minutes). > > - the grand computed total for all tasks becomes completely wrong (4:38 > instead of 4.5 + 0.125 = 4.625 days). > > Am I doing something wrong, or forgetting something? This should be fixed now. Thanks, -- Bastien