emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Bob Heffernan <bob.heffernan@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Problem with defining stuck projects
Date: Thu, 7 Jul 2022 17:32:00 +0100	[thread overview]
Message-ID: <20220707163200.ug43xhgzr52t5lyc@bob-mtu> (raw)

Dear all,

I am having trouble setting org-stuck-projects in a way that works for me.

My org-files are organised something like this...
* Non-project header
  - blah, blah
  ** Foo
* TODO Project 1
  ** TODO Do this
     CLOSED: [2022-07-06 Wed 17:10] SCHEDULED: <2022-07-06 Wed>
  ** TODO Do these
  *** TODO First thing
      CLOSED: [2022-07-06 Wed 17:20] SCHEDULED: <2022-07-06 Wed>
  *** TODO Second thing
* TODO Project 2
  ** TODO Something
     SCHEDULED: <2022-07-07 Thu>

I want the following:
  1. A project is a level 1 header marked as TODO
  2. A project is not stuck if it has any sub-header that is scheduled but not closed.

So, in the example above Project 1 counts as stuck, but Project 2 does not.

What I've got so far is this:
(setq org-stuck-projects
          '("+LEVEL=1/TODO-DONE" nil nil "SCHEDULED:")

But this will clearly mark both projects 1 and 2 as stuck.
I need some way of specifying the "but not closed" part, but am at a loss as to how I can do this.

Any help is appreciated.
Regards,
Bob Heffernan

next             reply	other threads:[~2022-07-07 16:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-07 16:32 Bob Heffernan [this message]
2022-07-08  4:51 ` Problem with defining stuck projects Ihor Radchenko
2022-07-08 14:37   ` Bob Heffernan

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=20220707163200.ug43xhgzr52t5lyc@bob-mtu \
    --to=bob.heffernan@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

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).