From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: FR: multiple scheduling of one item? Date: Thu, 3 Jan 2008 08:44:08 +0100 Message-ID: <43E2D02D-CF49-4074-98C0-58D93E7B05F3@gmail.com> References: <20071231152158.GN20947@atlantic.linksys.moosehall> Mime-Version: 1.0 (Apple Message framework v915) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JALKi-0002nC-1G for emacs-orgmode@gnu.org; Thu, 03 Jan 2008 03:21:44 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JALKg-0002lx-7l for emacs-orgmode@gnu.org; Thu, 03 Jan 2008 03:21:43 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JALKf-0002lh-HZ for emacs-orgmode@gnu.org; Thu, 03 Jan 2008 03:21:41 -0500 Received: from ug-out-1314.google.com ([66.249.92.170]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JALKf-0003AK-7J for emacs-orgmode@gnu.org; Thu, 03 Jan 2008 03:21:41 -0500 Received: by ug-out-1314.google.com with SMTP id a2so2989914ugf.48 for ; Thu, 03 Jan 2008 00:21:40 -0800 (PST) In-Reply-To: <20071231152158.GN20947@atlantic.linksys.moosehall> 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: Adam Spiers Cc: org-mode mailing list On Dec 31, 2007, at 4:21 PM, Adam Spiers wrote: > Imagine I have a single project or task which I know will require > several sessions to complete. Before I get to the stage of analysing > it closely and breaking it down into sub-tasks, it would be good to > reserve some diary time in advance, so that I don't accidentally > accept other commitments for that time and overstretch myself. > > However, this is different from booking a normal diary appointment, in > the sense that I am not making a commitment to other people to be in a > particular place at a particular time: the commitment is only to > myself and is directly associated with a particular project or task. > > Therefore it sounds like it would be useful to be able to schedule the > same task for multiple slots. It turns out that the org-agenda code > already handles this beautifully; if you do: > > * Long task/project not yet broken down into sub-tasks > SCHEDULED: <2008-01-07 Mon> > SCHEDULED: <2008-01-08 Tue> > > and it appears in both places in an agenda view, and you can jump back > to the item in the normal way. The only downside is that C-c C-s > doesn't currently support entering it: > > (org-schedule &optional REMOVE) > > Insert the SCHEDULED: string with a timestamp to schedule a TODO > item. > With argument REMOVE, remove any scheduling date from the item. > > How about doing the usual trick of comparing different prefix argument > values (e.g. 4 vs. 16) to allow adding a new scheduled slot? This could be done of course - but I am not sure how common your use case is. And I quess it is nearly as easy to got to the entry and type `SCHDEULED: C-c .' for the few cases where you need it? If I nt forward to implement this, should the extra SCHEDULED stamp be in the same second line of the entry, or in an extra line? Any other votes on this issue? - Carsten