From: Bernt Hansen <bernt@norang.ca>
To: "François Pinard" <pinard@iro.umontreal.ca>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: Recurring TODO spuriously blocked [7.7]
Date: Mon, 12 Dec 2011 12:35:18 -0500 [thread overview]
Message-ID: <87wra1lmll.fsf@norang.ca> (raw)
In-Reply-To: <87wra2mpij.fsf@iro.umontreal.ca> ("François Pinard"'s message of "Sun, 11 Dec 2011 22:34:44 -0500")
pinard@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
next prev parent reply other threads:[~2011-12-12 17:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-12 3:34 Bug: Recurring TODO spuriously blocked [7.7] François Pinard
2011-12-12 17:35 ` Bernt Hansen [this message]
2011-12-12 19:10 ` François Pinard
2011-12-13 0:44 ` Bernt Hansen
2011-12-13 1:33 ` François Pinard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wra1lmll.fsf@norang.ca \
--to=bernt@norang.ca \
--cc=emacs-orgmode@gnu.org \
--cc=pinard@iro.umontreal.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).