emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: devesh <right.ho@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: weird interplay between enforce dependencies, stuck projects and previous subtree [8.2.10 (8.2.10-23-g1ec416-elpa @ /home/devesh/.emacs.d/elpa/org-20141208/)]
Date: Mon, 10 Aug 2015 14:10:22 +0200	[thread overview]
Message-ID: <87egjbe441.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <874mkdwrmt.fsf@centos7.i-did-not-set--mail-host-address--so-tickle-me> (devesh's message of "Wed, 05 Aug 2015 23:21:22 +0530")

Hello,

devesh <right.ho@gmail.com> writes:

> When org-enforce-todo-dependencies is t, stuck projects definition is
> simply '("+project" ("NEXT") nil ""), and org mode file looks like :
>
> * A                                     :project:
>   :PROPERTIES:
>   :ORDERED:  t
>   :END:
> ** TODO B
> * C                          :project:
> ** TODO D
>
> Both A and C appear as stuck projects, which is expected behaviour.
>
> But if A itself becomes TODO, like below:
>
> * TODO A                                     :project:
>   :PROPERTIES:
>   :ORDERED:  t
>   :END:
> ** TODO B
> * C                          :project:
> ** TODO D
>
> Not only A vanishes from stuck projects, but C also vanishes. No stuck
> projects are shown for the above file.
>
> One subtree should not affect the next, even if first is ordered and
> org-enforce-todo-dependencies is t.

Could you update Org to latest ELPA version and test it again? It may
have been fixed since then.


Regards,

-- 
Nicolas Goaziou

      reply	other threads:[~2015-08-10 12:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-05 17:51 Bug: weird interplay between enforce dependencies, stuck projects and previous subtree [8.2.10 (8.2.10-23-g1ec416-elpa @ /home/devesh/.emacs.d/elpa/org-20141208/)] devesh
2015-08-10 12:10 ` Nicolas Goaziou [this message]

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=87egjbe441.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=right.ho@gmail.com \
    /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).