From ffd00c1272dd876f64c9ef930d19988b6da5c2a3 Mon Sep 17 00:00:00 2001 From: Stefan Kangas Date: Sun, 2 Oct 2022 21:54:20 +0200 Subject: [PATCH 1/3] Add crossreference to org-stuck-projects docstring * lisp/org-agenda.el (org-stuck-projects): Add Info manual reference to docstring. --- lisp/org-agenda.el | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/lisp/org-agenda.el b/lisp/org-agenda.el index e5df768ff..5b8133e81 100644 --- a/lisp/org-agenda.el +++ b/lisp/org-agenda.el @@ -614,13 +614,17 @@ you can then use it to define a custom command." '("+LEVEL=2/-DONE" ("TODO" "NEXT" "NEXTACTION") nil "") "How to identify stuck projects. This is a list of four items: + 1. A tags/todo/property matcher string that is used to identify a project. - See the manual for a description of tag and property searches. - The entire tree below a headline matched by this is considered one project. + See Info node `(org) Matching tags and properties' for a + description of tag and property searches. The entire tree + below a headline matched by this is considered one project. + 2. A list of TODO keywords identifying non-stuck projects. If the project subtree contains any headline with one of these todo keywords, the project is considered to be not stuck. If you specify \"*\" as a keyword, any TODO keyword will mark the project unstuck. + 3. A list of tags identifying non-stuck projects. If the project subtree contains any headline with one of these tags, the project is considered to be not stuck. If you specify \"*\" as @@ -628,6 +632,7 @@ This is a list of four items: the explicit presence of a tag somewhere in the subtree, inherited tags do not count here. If inherited tags make a project not stuck, use \"-TAG\" in the tags part of the matcher under (1.) above. + 4. An arbitrary regular expression matching non-stuck projects. If the project turns out to be not stuck, search continues also in the -- 2.30.2