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?
