From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bernt Hansen <bernt@norang.ca>
Subject: Re: Bug: Recurring TODO spuriously blocked [7.7]
Date: Mon, 12 Dec 2011 12:35:18 -0500
Message-ID: <87wra1lmll.fsf@norang.ca>
References: <87wra2mpij.fsf@iro.umontreal.ca>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([140.186.70.92]:38252)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <bernt@norang.ca>) id 1Ra9mj-0008EH-39
	for emacs-orgmode@gnu.org; Mon, 12 Dec 2011 12:35:34 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <bernt@norang.ca>) id 1Ra9me-0004To-RD
	for emacs-orgmode@gnu.org; Mon, 12 Dec 2011 12:35:29 -0500
Received: from mho-03-ewr.mailhop.org ([204.13.248.66]:56712
	helo=mho-01-ewr.mailhop.org) by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <bernt@norang.ca>) id 1Ra9me-0004Tj-O7
	for emacs-orgmode@gnu.org; Mon, 12 Dec 2011 12:35:24 -0500
In-Reply-To: <87wra2mpij.fsf@iro.umontreal.ca> (=?utf-8?Q?=22Fran=C3=A7ois?=
	Pinard"'s message of "Sun, 11 Dec 2011 22:34:44 -0500")
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: =?utf-8?Q?Fran=C3=A7ois?= Pinard <pinard@iro.umontreal.ca>
Cc: emacs-orgmode@gnu.org

pinard@iro.umontreal.ca (Fran=C3=A7ois 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