From: Ihor Radchenko <yantar92@gmail.com>
To: Bob Heffernan <bob.heffernan@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Problem with defining stuck projects
Date: Fri, 08 Jul 2022 12:51:47 +0800 [thread overview]
Message-ID: <87v8s82om4.fsf@localhost> (raw)
In-Reply-To: <20220707163200.ug43xhgzr52t5lyc@bob-mtu>
Bob Heffernan <bob.heffernan@gmail.com> writes:
> 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.
If you have org-log-done set to 'time, your completed (closed) tasks
will contain CLOSED: ... in their planning line:
* DONE headline
CLOSED: [timestamp] SCHEDULED: [timestamp]
So, you can try the following regexp instead of "SCHEDULED:":
"^[ \t]*\\(SCHEDULED:\\|DEADLINE:\\)"
Best,
Ihor
next prev parent reply other threads:[~2022-07-08 4:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 16:32 Problem with defining stuck projects Bob Heffernan
2022-07-08 4:51 ` Ihor Radchenko [this message]
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=87v8s82om4.fsf@localhost \
--to=yantar92@gmail.com \
--cc=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
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).