From: Ihor Radchenko <yantar92@posteo.net>
To: Kevin Layer <layer@known.net>
Cc: Emacs-orgmode@gnu.org
Subject: Re: Specialized sparse-tree via hook to show specific view in org mode
Date: Tue, 07 Feb 2023 20:28:34 +0000 [thread overview]
Message-ID: <87h6vxdxu5.fsf@localhost> (raw)
In-Reply-To: <CAGSZTjLLP9zgsiDrpYoPYF7OaqD7JMwiJO+CdR+b9uKDgZbyxw@mail.gmail.com>
Kevin Layer <layer@known.net> writes:
> My main todo file defines various TODO keywords and initial state like this:
>
> #+STARTUP: indent overview
> #+TODO: @NOW @NEXT @WIP @PENDING
>
> What I really want is to initially only see items noted with those TODO
> keywords and also due items. Everything else should be hidden.
I think you can use `org-match-sparse-tree'. It supports the general
match syntax. See 11.3.3 Matching tags and properties section for the
match syntax.
> If this is the right way and the maintainer wants me to submit a patch, I
> would include these functions to get a new optional for keep-previous,
> since they could all plausibly be used for the same thing that
> org-check-before-date was:
> * org-show-todo-tree
> * org-check-deadlines
> * org-check-before-date
> * org-check-after-date
> * org-check-dates-range
I think that it does make sense to support KEEP-PREVIOUS in these
functions. `org-occur' does support it and there is no reason not to
allow the same toggle in the listed functions.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
prev parent reply other threads:[~2023-02-07 20:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 1:12 Specialized sparse-tree via hook to show specific view in org mode Kevin Layer
2023-02-07 20:28 ` Ihor Radchenko [this message]
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=87h6vxdxu5.fsf@localhost \
--to=yantar92@posteo.net \
--cc=Emacs-orgmode@gnu.org \
--cc=layer@known.net \
/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).