emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jude DaShiell <jdashiel@panix.com>
To: Martin Schroeder <mkschreder.uk@googlemail.com>, emacs-orgmode@gnu.org
Subject: Re: Incorrect clock duration calculation
Date: Tue, 7 May 2019 10:07:34 -0400	[thread overview]
Message-ID: <alpine.NEB.2.21.1905071006470.16588@panix1.panix.com> (raw)
In-Reply-To: <CAGmj6qvs+W==0quSrkXs9cvE5Le7E3Onhe757xR3XzR+KBQe2Q@mail.gmail.com>

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 <mkschreder.uk@googlemail.com>
> 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?
>
>

-- 

  parent reply	other threads:[~2019-05-07 14:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-07  9:07 Incorrect clock duration calculation Martin Schroeder
2019-05-07 14:02 ` Julius Dittmar
2019-05-07 14:07 ` Jude DaShiell [this message]
2019-05-07 19:30 ` Thomas Plass

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.NEB.2.21.1905071006470.16588@panix1.panix.com \
    --to=jdashiel@panix.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mkschreder.uk@googlemail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).