From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: FR: multiple scheduling of one item? Date: Mon, 07 Jan 2008 02:52:51 +0000 Message-ID: <87lk72fit8.fsf@bzg.ath.cx> References: <20071231152158.GN20947@atlantic.linksys.moosehall> <43E2D02D-CF49-4074-98C0-58D93E7B05F3@gmail.com> <20080103223921.GB4991@fastwebnet.it> <20080104095502.GH18716@atlantic.linksys.moosehall> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JBi6q-00024M-4h for emacs-orgmode@gnu.org; Sun, 06 Jan 2008 21:53:04 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JBi6l-000239-Av for emacs-orgmode@gnu.org; Sun, 06 Jan 2008 21:53:03 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JBi6l-000236-7Z for emacs-orgmode@gnu.org; Sun, 06 Jan 2008 21:52:59 -0500 Received: from fg-out-1718.google.com ([72.14.220.159]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JBi6k-0000If-Ux for emacs-orgmode@gnu.org; Sun, 06 Jan 2008 21:52:59 -0500 Received: by fg-out-1718.google.com with SMTP id d23so4588660fga.30 for ; Sun, 06 Jan 2008 18:52:58 -0800 (PST) In-Reply-To: <20080104095502.GH18716@atlantic.linksys.moosehall> (Adam Spiers's message of "Fri, 4 Jan 2008 09:55:02 +0000") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 Adam Spiers 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".) BTW, there is a small bug when trying to enter the SCHEDULED property by hand: the sequence `C-c C-x p SCHEDULED RET' will ask for a value, then discard it and ask again for a date (thru org-read-date). I guess it should ask for the date only. -- Bastien