emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Rakestraw <lists@johnrakestraw.com>
To: Carsten Dominik <dominik@science.uva.nl>
Cc: emacs-orgmode@gnu.org
Subject: Re: Can't make TODO dependencies work
Date: Sun, 1 Feb 2009 13:23:10 -0500	[thread overview]
Message-ID: <20090201132310.57b6e384@johnrakestraw.com> (raw)
In-Reply-To: <941FA03B-2A6D-40ED-8D4B-A5657BEA9798@uva.nl>

On Sun, 1 Feb 2009 19:03:46 +0100
Carsten Dominik <dominik@science.uva.nl> wrote:

> > This is misleading. I realized that dependencies *do* work  
> > consistently
> > in the minimal configuration. With the header line in the test
> > file, I can change the main task from TODO to STARTED (or to any of
> > the other non-done states), but I'm blocked from changing it to
> > DONE.  
> 
> This is how it should be.

I agree -- that's why I apologized for introducing that point.
> 
> > But they still don't work with my usual configuration.  
> 
> Well, if the value of org-blocker-hook is nil in this case, I
> am not surprised!   Why is it nil?  If you set the
> org-enforce... variables, the hook should be filled
> with the two functions.

I don't know why it's nil. However, I've discovered a bit more. It
seems that the problem is that my settings in my org-config file:

(setq org-enforce-todo-dependencies t)
(setq org-agenda-dim-blocked-tasks 'invisible)
(setq org-enforce-todo-checkbox-dependencies t)

didn't prompt the required change in the value of org-blocker-hook.
With these lines in my org config file, the values of the three
variables are as expected, but the value of org-blocker-hook remains
nil, even if I stop and re-start emacs.

When I change the value of org-enforce-todo-dependencies using
customize, then the value of org-blocker-hook is what it should be, and
the dependencies work, even if I stop and re-start emacs.

So presumably something else in my config file is keeping
org-blocker-hook from being re-set?

I'd prefer not to use the customize function, so I'd hoped to set it in
my config file.

Thanks, and apologies for not sorting through this a bit more before
the initial post.

--John

  parent reply	other threads:[~2009-02-01 18:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090201121412.657196d2@johnrakestraw.com>
2009-02-01 17:21 ` Can't make TODO dependencies work Carsten Dominik
2009-02-01 17:45 ` John Rakestraw
     [not found]   ` <941FA03B-2A6D-40ED-8D4B-A5657BEA9798@uva.nl>
2009-02-01 18:23     ` John Rakestraw [this message]
2009-02-01 19:21       ` Carsten Dominik
2009-02-01 19:38         ` Carsten Dominik
2009-02-01 20:27           ` John Rakestraw
2009-02-02  7:13           ` Paul Mead
2009-02-02 16:05           ` Wes Hardaker
2009-02-02 21:08             ` Carsten Dominik
2009-02-02 22:35               ` Wes Hardaker

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=20090201132310.57b6e384@johnrakestraw.com \
    --to=lists@johnrakestraw.com \
    --cc=dominik@science.uva.nl \
    --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).