From: Daniel Hochheimer <dh@obyz.de>
To: emacs-orgmode@gnu.org
Subject: bug in "simple dependencies" handling (?)
Date: Tue, 24 Mar 2009 20:13:46 +0100 [thread overview]
Message-ID: <49C930EA.2000205@obyz.de> (raw)
Hello,
first of all, please excuse my poorly english.
It seems there is a bug in the handling of simple dependencies.
I think an example tree is the best solution, to show you the bug:
* Projects
#+CATEGORY: Projects
*** TODO foo bar project
:PROPERTIES:
:ORDERED: t
:END:
***** TODO foo subproject :FooSubproject:
******* TODO Task 1
***** TODO bar subproject :BarSubproject:
******* TODO Task 1
This is in my .emacs file:
(setq org-enforce-todo-dependencies t)
(setq org-agenda-dim-blocked-tasks 'invisible)
(setq org-odd-levels-only t)
the expected global todo agenda view imho is:
Projects: Task 1 :FooSubproject:
but actual it is unfortunately:
Projects: Task 1 :FooSubproject:
Projects: Task 1 :BarSubproject:
Imho "Task 1" from "bar subproject" should not be visible,
because "bar subproject " is blocked because of the
ORDERED property (therefore it's childs should be blocked, too)
Is it easy / possible to fix this bug? My whole GTD system is
heavily based on such project / subproject-Constructs. But with
this bug my global todo agenda view is unfortunately "polluted"
a little bit with tasks from projects that shouldn't be active.
Best regards,
Daniel
PS: many thanks to the developer of this great emacs mode, I really
enjoy org-mode. I started using emacs only because of the great
abilities of org-mode.
next reply other threads:[~2009-03-24 19:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 19:13 Daniel Hochheimer [this message]
2009-03-26 15:43 ` bug in "simple dependencies" handling (?) Carsten Dominik
2009-03-27 0:24 ` Daniel
2009-03-27 14:05 ` Carsten Dominik
2009-03-28 2:52 ` Daniel
2009-03-30 14:39 ` Carsten Dominik
2009-04-01 20:02 ` Daniel
2009-04-03 16:58 ` Carsten Dominik
2009-04-07 19:59 ` Daniel
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=49C930EA.2000205@obyz.de \
--to=dh@obyz.de \
--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).