emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bernt Hansen <bernt@norang.ca>
To: John J Foerch <jjfoerch@earthlink.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-evaluate-time-range
Date: Tue, 28 Jun 2011 18:57:10 -0400	[thread overview]
Message-ID: <87ei2dr2d5.fsf@norang.ca> (raw)
In-Reply-To: <87k4c5agb7.fsf@hecubus.retroj.net> (John J. Foerch's message of "Tue, 28 Jun 2011 15:47:56 -0400")

John J Foerch <jjfoerch@earthlink.net> writes:

> Hello,
> I have a question about the use-case for org-evaluate-time-range,
> because for what I would use it for, its behavior seems
> counter-intuitive.  Consider a time range:
>     <2011-08-12 Fri>--<2011-08-14 Sun>
> Calling org-evaluate-time-range on this range reports 2 days, but for
> situations when I would use time ranges, I would have expected an
> _inclusive_ count of 3 days.  The span represented from a friday through
> a sunday is indeed a span of 3 days.
> Can anyone explain the logic behind the current behavior?  Thank you.

Timestamps with no time are considered to be at midnight (00:00)

So Midnight Friday to Midnight Sunday is 48 hours.



      reply	other threads:[~2011-06-28 22:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-28 19:47 org-evaluate-time-range John J Foerch
2011-06-28 22:57 ` Bernt Hansen [this message]

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:

  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=87ei2dr2d5.fsf@norang.ca \
    --to=bernt@norang.ca \
    --cc=emacs-orgmode@gnu.org \
    --cc=jjfoerch@earthlink.net \


* 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


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).