From 412f0406da6366b0d956a8c45ed8433eea5ab09a Mon Sep 17 00:00:00 2001 From: Bastien Date: Sat, 23 May 2020 15:39:30 +0200 Subject: [PATCH] doc/org-manual.org: Mention `stuck' as an available agenda view * doc/org-manual.org (Block agenda): Mention `stuck' as an available agenda view for a block agenda. --- doc/org-manual.org | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/doc/org-manual.org b/doc/org-manual.org index d90900600..146cf6954 100644 --- a/doc/org-manual.org +++ b/doc/org-manual.org @@ -10304,8 +10304,10 @@ Another possibility is the construction of agenda views that comprise the results of /several/ commands, each of which creates a block in the agenda buffer. The available commands include ~agenda~ for the daily or weekly agenda (as created with {{{kbd(a)}}}) , ~alltodo~ for -the global TODO list (as constructed with {{{kbd(t)}}}), and the +the global TODO list (as constructed with {{{kbd(t)}}}), ~stuck~ for +the list of stuck projects (as obtained with {{{kbd(#)}}}) and the matching commands discussed above: ~todo~, ~tags~, and ~tags-todo~. + Here are two examples: #+begin_src emacs-lisp