From mboxrd@z Thu Jan  1 00:00:00 1970
From: =?utf-8?Q?S=C3=A9bastien_Vauban?= <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
Subject: Re: TODO state change from TODO to DONE blocked
Date: Fri, 04 Mar 2011 16:01:47 +0100
Message-ID: <80hbbjq690.fsf@somewhere.org>
References: <80lj15yab6.fsf@somewhere.org> <80wrkp4dwo.fsf@somewhere.org>
	<87pqqeafov.fsf@gnu.org>
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-mXXj517/zsQ@public.gmane.org>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request-mXXj517/zsQ@public.gmane.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode-mXXj517/zsQ@public.gmane.org>
List-Help: <mailto:emacs-orgmode-request-mXXj517/zsQ@public.gmane.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request-mXXj517/zsQ@public.gmane.org?subject=subscribe>
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org

Hi Bastien,

Bastien wrote:
>>> I've a really weird exception occurring: change state from TODO to DONE=
 is
>>> blocked... while I'm on a leaf of the Org tree!?
>>>
>>> Debugger entered--Lisp error: (error #("TODO state change from TODO to
>>> DONE blocked" 23 27 (face org-todo) 31 35 (face org-done)))
>
> Are you using `org-blocker-hook' or `org-trigger-hook'?

Nope. Never heard of them.

> Maybe you can try to `edebug-defun' the `org-todo' function and follow it=
's
> execution step by step.

Did it, but not obvious to follow -- I don't talk of the code itself, but of
my edebug skills.

> Let us know.

Though, hopping from one variable description to another, I remembered that=
 I
had set the variable =3Dorg-enforce-todo-dependencies=3D to =3Dt=3D. Trying=
 to set it
to =3Dnil=3D made the problem disappear... So, it was a bit narrowed.

I could see in the description of that var that it could block state change=
 if
tasks were ordered and a previous one not done. But I never use the ordered
property.

... Well, never, but well in that parent tree. Was it for test purpose?  Di=
d I
have something else in mind?  I dunno anymore, but that property was
definitely the culprit.

Doing so, I'm wondering:

- if the output message could be updated to make it clear what the reason i=
s,
  or can be?

- why it allowed me to update the tasks state when I narrowed the buffer to
  that task only? Does that mean that *narrowing* somehow *drops the inheri=
ted
  properties*?

Anyway, my fault...

Best regards,
  Seb

--=20
S=C3=A9bastien Vauban