From mboxrd@z Thu Jan  1 00:00:00 1970
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Re: Easy entry of date ranges
Date: Thu, 27 Aug 2015 10:15:16 +0200
Message-ID: <87vbc1jgff.fsf@nicolasgoaziou.fr>
References: <m2zj1eeyvo.fsf@gmail.com> <87egip50se.fsf@nicolasgoaziou.fr>
	<m2twrlg4yl.fsf@gmail.com> <87io815r7r.fsf@ericabrahamsen.net>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:47248)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mail@nicolasgoaziou.fr>) id 1ZUsJW-0001W8-5I
	for emacs-orgmode@gnu.org; Thu, 27 Aug 2015 04:13:44 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <mail@nicolasgoaziou.fr>) id 1ZUsJV-0008VI-6f
	for emacs-orgmode@gnu.org; Thu, 27 Aug 2015 04:13:38 -0400
Received: from relay4-d.mail.gandi.net ([2001:4b98:c:538::196]:42987)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mail@nicolasgoaziou.fr>) id 1ZUsJV-0008U0-0L
	for emacs-orgmode@gnu.org; Thu, 27 Aug 2015 04:13:37 -0400
In-Reply-To: <87io815r7r.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of
	"Thu, 27 Aug 2015 11:46:00 +0800")
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: emacs-orgmode@gnu.org

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

> Ken Mankoff <mankoff@gmail.com> writes:
>
>> No, scheduled + deadline is a different use case. The syntax I use,
>> =SCHEDULED: <2020-01-01>--<2020-01-07>=, is valid,

I wouldn't bet on it. I'm sure this can lead to subtle problems. For
example,

  * Test
    SCHEDULED: <2020-01-01>--<2020-01-07>

(org-entry-get (point-min) "SCHEDULED") => <2020-01-01>, i.e, range end
information is lost.

>>. One (of many) use cases: a week long vacation.
>> This use case is supported by Org since the Agenda helpfully shows
>> "(1/7)", and "(2/7)", etc. before each entry. Everything else is so
>> efficient and has shortcuts, including time ranges, I just hoped I was
>> missing something here. Perhaps it hasn't been implemented yet.
>
> I think what Nicolas means is that, in the sort of use case you're
> outlining above, you should probably be using a plain timestamp.
> SCHEDULED means "I'm going to work on this TODO now", in which case
> a time span doesn't quite make sense -- you start working at the start
> of the span, and you finish when you toggle the keyword to DONE. For
> a vacation, a plain timestamp is more appropriate.

Exactly.

If you know the exact range, use a plain timestamp. SCHEDULED is for
when you know when to start, but not when to end. With
SCHEDULED + DEADLINE, you know when to start, you're not sure when to
end, but it must be done before deadline.

Regards,