all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: Edmund Potts <edmundpotts@googlemail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Custom TODO keywords and org-enforce-todo-dependencies
Date: Sat, 11 Jun 2022 16:13:59 +0800	[thread overview]
Message-ID: <87tu8rbos8.fsf@localhost> (raw)
In-Reply-To: <CAO4jr0E_pENyanPW-asoc=xLyxNtcaTQXnvcYOt6-Ghnt1mY5w@mail.gmail.com>

Edmund Potts <edmundpotts@googlemail.com> writes:

> I have read the manual and searched the list archives but not found an
> answer to this - so apologies if it was in fact covered somewhere.
>
> I make use of the variable org-enforce-todo-dependencies along with the
> :ORDERED: property to have sequentially limited TODO lists.
>
> However I found when experimenting with custom TODO keywords that once they
> were enabled, the blocking functionality did not work. I was able to change
> any of my TODO headers to "DONE", regardless of the state of the TODO item
> immediately preceding them.
>
> Is there a way these two functions can work together? I would appreciate
> any guidance.

Sorry for the late reply. Hope it is still relevant.

ORDERED + org-enforce-todo-depenencies should work with custom TODO
keywords as long as you properly define which keywords mean that a task
is 'done and which keywords mean the opposite.

org-todo-keywords:

Each sequence starts with a symbol, either sequence or type,
indicating if the keywords should be interpreted as a sequence of
action steps, or as different types of TODO items.  The first
keywords are states requiring action - these states will select a headline
for inclusion into the global TODO list Org produces.  If one of the
"keywords" is the vertical bar, "|", the remaining keywords
signify that no further action is necessary.  If "|" is not found,
the last keyword is treated as the only DONE state of the sequence.

Best,
Ihor


      reply	other threads:[~2022-06-11  8:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-06 14:29 Custom TODO keywords and org-enforce-todo-dependencies Edmund Potts
2022-06-11  8:13 ` Ihor Radchenko [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87tu8rbos8.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=edmundpotts@googlemail.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.