From: "Sébastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Re: TODO state change from TODO to DONE blocked
Date: Fri, 04 Mar 2011 22:52:53 +0100 [thread overview]
Message-ID: <80ei6mmu2y.fsf@somewhere.org> (raw)
In-Reply-To: 87hbbiuane.fsf@norang.ca
Hi Bernt,
Bernt Hansen wrote:
> Sébastien Vauban <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw-XMD5yJDbdMSQIYZ4X/+iSw@public.gmane.orgrg> writes:
>> 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)))
>
> <snip>
>
>> 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? Did 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 is,
>> 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 inherited
>> properties*?
>
> If narrowing the buffer allows the state change when the parent (outside the
> narrowed region) has the ORDERED property - I think that's a bug that needs
> to be fixed.
Yes, it does. That has been my workaround once -- before searching more to
find the root cause.
> The behaviour shouldn't change if you narrow the buffer.
We share the same point of view.
Best regards,
Seb
--
Sébastien Vauban
next prev parent reply other threads:[~2011-03-04 21:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-24 10:51 TODO state change from TODO to DONE blocked Sébastien Vauban
2011-02-24 16:04 ` Sébastien Vauban
2011-02-26 17:06 ` Bastien
2011-03-04 15:01 ` Sébastien Vauban
2011-03-04 15:15 ` [PATCH] " Sébastien Vauban
2011-03-04 18:46 ` Bastien
2011-03-04 21:54 ` Sébastien Vauban
2011-03-05 10:02 ` Bastien
2011-03-04 16:13 ` Bernt Hansen
2011-03-04 21:52 ` Sébastien Vauban [this message]
2011-03-05 10:03 ` Bastien
2011-03-05 11:10 ` Bernt Hansen
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=80ei6mmu2y.fsf@somewhere.org \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \
/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).