From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jude DaShiell Subject: Re: Incorrect clock duration calculation Date: Tue, 7 May 2019 10:07:34 -0400 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Return-path: Received: from eggs.gnu.org ([209.51.188.92]:42551) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hO0ks-0006i6-8U for emacs-orgmode@gnu.org; Tue, 07 May 2019 10:07:39 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hO0kq-00053j-Un for emacs-orgmode@gnu.org; Tue, 07 May 2019 10:07:38 -0400 Received: from mailbackend.panix.com ([166.84.1.89]:55733) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hO0kq-00051Q-QG for emacs-orgmode@gnu.org; Tue, 07 May 2019 10:07:36 -0400 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: Martin Schroeder , emacs-orgmode@gnu.org Duration must not endure for more than 24 hours since that's unendoreable. On Tue, 7 May 2019, Martin Schroeder wrote: > Date: Tue, 7 May 2019 05:07:58 > From: Martin Schroeder > To: emacs-orgmode@gnu.org > Subject: [O] Incorrect clock duration calculation > > I noticed that on timestamps that begin or end at 00:00 the org mode > org-evaluate-time-range function seems to produce wrong results. Here > are some examples: > > For example, this should produce 2:00 duration: > CLOCK: [2019-04-19 Fri 22:00]--[2019-04-19 Fri 00:00] => -22:00 > I tried this, but id did not work either: > CLOCK: [2019-04-19 Fri 22:00]--[2019-04-19 Sat 00:00] => -22:00 > This works though but this does not cross day boundary: > CLOCK: [2019-04-19 Fri 22:00]--[2019-04-19 Fri 23:00] => 1:00 > This should produce 3:00 but it gives -21 even though the end time is > later than start time: > CLOCK: [2019-04-19 Fri 22:00]--[2019-04-19 Sat 01:00] => -21:00 > > Does anyone have a solution for this? > > --