pin...@iro.umontreal.ca (François Pinard) writes: > > Whenever a TODO is scheduled with a recurrence (with .+ or ++), forcing > the state to DONE is a mere way to trigger Org into setting the state to > TODO again, yet with the scheduled date updated for the next repetition. > Setting to DONE merely means that this repetition is done, which is not > the same as being forever DONE. In fact, setting a repeated schedule to > DONE is really a way of updating the schedule; the intent relies on the > mechanics by which the DONE state is just a transient way to TODO again. > > Now, within ~/.emacs, I have org-enforce-todo-dependencies set to t, for > good purposes. But then, I get spurious: > > byte-code: TODO state change from TODO to DONE blocked > > trying to schedule the next repetition. todo-dependencies should likely > never be enforced for repeated entries, even if enforced otherwise, as > enforcing for repetitions with the current Org mechanics has no meaning, > at least as I undestand Org so far.
You can set a NOBLOCKING property to t to skip the dependency check for repeated tasks. * TODO Some Repeating Task SCHEDULED: <2011-12-16 Fri 15:30 ++1w> :PROPERTY: :NOBLOCKING: t :END: Regards, Bernt
