[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] Incorrect clock duration calculation
From: |
Jude DaShiell |
Subject: |
Re: [O] Incorrect clock duration calculation |
Date: |
Tue, 7 May 2019 10:07:34 -0400 |
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 <address@hidden>
> To: address@hidden
> 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?
>
>
--