On Mon, Jan 07, 2008 at 02:52:51AM +0000, Bastien wrote: > Adam Spiers <[EMAIL PROTECTED]> 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. _______________________________________________ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
