From: Allen Li <vianchielfaura@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Bug: ordered property blocks grandchildren [9.1.3 (9.1.3-elpaplus @ ~/.emacs.d/elpa/org-plus-contrib-20171116/)]
Date: Mon, 27 Nov 2017 12:01:40 -0800 [thread overview]
Message-ID: <CAJr1M6edxDR2fKjiMEV2jV1JjQr8JYwhnCScDdHT0h_+xhXntw@mail.gmail.com> (raw)
In-Reply-To: <CAJr1M6dtX6fXiT1ixupmHbxTSUZVZ6xK2knLXra9=qeyuFQc5A@mail.gmail.com>
On Mon, Nov 20, 2017 at 5:18 PM, Allen Li <vianchielfaura@gmail.com> wrote:
> Create a file tmp.org with contents
>
> * TODO parent
> :PROPERTIES:
> :ORDERED: t
> :END:
> ** TODO child1
> ** TODO child2
> *** TODO grandchild1
> *** TODO grandchild2
>
> 1. emacs -Q
> 2. M-: (setq org-enforce-todo-dependencies t) RET
> 3. C-x C-f tmp.org RET
> 4. Move point to grandchild2
> 5. C-c C-t
>
> user-error: TODO state change from TODO to DONE blocked (by "TODO child1")
>
> The documentation emphasizes that ORDERED is not inherited. The
> behavior that I would expect is that child1 blocks child2, but it should
> not block grandchild1 or grandchild2.
>
> However, I think the current behavior is also reasonable under some
> workflows. I’m creating a bug to track opinions, if one behavior is
> significantly more desired than the other, or if an option to control
> this behavior would be welcome.
There's an additional quirk to this behavior:
If the child is not a TODO heading, its grandchildren are not blocked
* TODO parent
:PROPERTIES:
:ORDERED: t
:END:
** TODO child1
** child2
*** TODO grandchild1
*** TODO grandchild2
In this modified example, the grandchildren are not blocked, unlike
the original example. Again I can see certain workflows relying on
this behavior, but the behavior isn't quite obvious. The
documentation should probably be improved. I'd also like to think
about the implications behind this behavior and any alternatives a
little more.
next prev parent reply other threads:[~2017-11-27 20:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-21 1:18 Bug: ordered property blocks grandchildren [9.1.3 (9.1.3-elpaplus @ ~/.emacs.d/elpa/org-plus-contrib-20171116/)] Allen Li
2017-11-27 20:01 ` Allen Li [this message]
2018-04-26 23:34 ` Bastien
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=CAJr1M6edxDR2fKjiMEV2jV1JjQr8JYwhnCScDdHT0h_+xhXntw@mail.gmail.com \
--to=vianchielfaura@gmail.com \
--cc=emacs-orgmode@gnu.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).