From mboxrd@z Thu Jan  1 00:00:00 1970
From: Adam Spiers <orgmode@adamspiers.org>
Subject: Re: FR: multiple scheduling of one item?
Date: Mon, 7 Jan 2008 10:14:41 +0000
Message-ID: <20080107101441.GJ18716@atlantic.linksys.moosehall>
References: <20071231152158.GN20947@atlantic.linksys.moosehall>
	<43E2D02D-CF49-4074-98C0-58D93E7B05F3@gmail.com>
	<20080103223921.GB4991@fastwebnet.it>
	<20080104095502.GH18716@atlantic.linksys.moosehall>
	<87lk72fit8.fsf@bzg.ath.cx>
Reply-To: Adam Spiers <orgmode@adamspiers.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1JBp0S-0000pf-Ko
	for emacs-orgmode@gnu.org; Mon, 07 Jan 2008 05:14:56 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1JBp0J-0000dT-0q
	for emacs-orgmode@gnu.org; Mon, 07 Jan 2008 05:14:48 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1JBp0H-0000cS-R7
	for emacs-orgmode@gnu.org; Mon, 07 Jan 2008 05:14:45 -0500
Received: from mail.beimborn.com ([70.84.38.100])
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60)
	(envelope-from <f5-sendmail@adamspiers.org>) id 1JBp0H-0007n8-IN
	for emacs-orgmode@gnu.org; Mon, 07 Jan 2008 05:14:45 -0500
Received: from mail.beimborn.com (localhost.localdomain [127.0.0.1])
	by mail.beimborn.com (8.12.11.20060308/8.12.8) with ESMTP id
	m07AEhu5024150
	for <emacs-orgmode@gnu.org>; Mon, 7 Jan 2008 04:14:43 -0600
Received: from localhost (localhost [[UNIX: localhost]])
	by mail.beimborn.com (8.12.11.20060308/8.12.11/Submit) id
	m07AEhMp024144
	for emacs-orgmode@gnu.org; Mon, 7 Jan 2008 10:14:43 GMT
Content-Disposition: inline
In-Reply-To: <87lk72fit8.fsf@bzg.ath.cx>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: emacs-orgmode@gnu.org

On Mon, Jan 07, 2008 at 02:52:51AM +0000, Bastien wrote:
> Adam Spiers <orgmode@adamspiers.org> writes:
> 
> > That's a nice idea, but it won't cover all eventualities,
> > e.g. sometimes one would need:
> >
> >   * Long task
> >     SCHEDULED: <2008-01-07 Mon 10:00-13:00>
> >     SCHEDULED: <2008-01-08 Tue 14:00-17:00>
> 
> FWIW, I think it would be better to have something like this:
> 
> ,----
> | * Something important
> |   SCHEDULED: <2008-01-06 dim 9:00-13:00>
> | 
> |   :PROPERTIES:
> |   :SCHEDULED: <2008-01-07 lun 9:00-13:00>, <2008-01-08 mar 9:00-13:00>
> |   :END:
> `----
> 
> Org would first check the "SCHEDULED:" cookie, then check for further
> re-schedulding (the property might also be called "RESCHEDULDED".)

Whilst tracking re-scheduling might be useful, it wasn't my intention.
I wanted to be able to create a schedule in advance which spans
multiple sessions.