From: Ruslan Bekenev <furyinbox@gmail.com>
To: emacs-orgmode@gnu.org
Subject: [PATCH] Add missing "stuck" agenda view to Special Agenda Views section of manual
Date: Sat, 8 Apr 2023 18:48:51 +1000 [thread overview]
Message-ID: <4FF692D3-2752-4CFE-A095-EFE3AA320187@gmail.com> (raw)
Hi guys,
I’ve been trying to make my custom agenda view and I really wanted to see the list of stuck projects in there.
Looking at “Special Agenda Views” section of the manual I was sure there is no ~stuck~ special view because it isn’t mentioned there.
Turned out there is such a view, it just mentioned in “Block agenda” section of the manual.
I think "Special Agenda Views” section must also mention ~stuck~ as an option.
The patch below just adds it.
Let me know if it makes any sense.
Thanks,
Ruslan
From 7ffa93aa66eab099d7c41d0d1c99aa97818fd39e Mon Sep 17 00:00:00 2001
From: Ruslan Bekenev <furyinbox@gmail.com>
Date: Sat, 8 Apr 2023 17:38:40 +1000
Subject: [PATCH] doc/org-manual.org; Add missing ~stuck~ agenda view
---
doc/org-manual.org | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/org-manual.org b/doc/org-manual.org
index 4644e5adc..4881b9a76 100644
--- a/doc/org-manual.org
+++ b/doc/org-manual.org
@@ -21441,7 +21441,7 @@ Org provides a special hook to further limit items in agenda views:
~agenda~, ~agenda*~[fn:: The ~agenda*~ view is the same as ~agenda~
except that it only considers /appointments/, i.e., scheduled and
deadline items that have a time specification =[h]h:mm= in their
-time-stamps.], ~todo~, ~alltodo~, ~tags~, ~tags-todo~, ~tags-tree~.
+time-stamps.], ~todo~, ~alltodo~, ~tags~, ~tags-todo~, ~tags-tree~, ~stuck~.
Specify a custom function that tests inclusion of every matched item
in the view. This function can also skip as much as is needed.
--
2.37.1 (Apple Git-137.1)
next reply other threads:[~2023-04-08 8:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-08 8:48 Ruslan Bekenev [this message]
2023-04-08 10:42 ` [PATCH] Add missing "stuck" agenda view to Special Agenda Views section of manual Ihor Radchenko
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=4FF692D3-2752-4CFE-A095-EFE3AA320187@gmail.com \
--to=furyinbox@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).