From: Kyle Meyer <firstname.lastname@example.org>
To: Stig Brautaset <email@example.com>
Subject: Re: tags-todo org-agenda-custom-command weirdness
Date: Tue, 16 Jun 2020 05:11:29 +0000 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Stig Brautaset writes:
> For me a2 and a4 returns the same, but a1 and a3 just returns TODO h2.
> However, I can reproduce what you're seeing by setting this:
> (setq org-agenda-todo-ignore-scheduled nil)
So, provided you've configured org-agenda-todo-ignore-scheduled and
org-agenda-tags-todo-honor-ignore-options away from their default values
of nil, the a1-4 behavior you described is as advertised, correct?
>> b1 and b3 are empty, which I think is expected given the tags-todo type.
> Well, I disagree :-)
> This behaviour of `tags-todo` seems inconsistent to me. If `todo` can
> find DONE items, why shouldn't `tags-todo` do the same?
Perhaps it should. The behavior has been that way for a long time, and
the code makes it look very deliberate. That of course is not an
argument that it should be that way, just one basis for expectations
(and a reason to be wary of breaking workflows).
And it looks like it was actually supposed to change to your preference
in 2017. There was a report  that essentially boils down to what
you're saying, I think. In response, 942b6267a (org-agenda: `tags-todo'
command type includes DONE keywords, 2017-04-18) was applied, but then
reverted for reasons not related to the intended change in behavior .
There was then a follow-up in 2fb129b5c (`org-scan-tags' retrieve all
TODO keywords, not only not-done ones, 2017-08-17). As far as I can
tell, that was supposed to achieve the behavior you're after but didn't.
I don't have time to dig much at the moment, but quickly stepping
through org-scan-tags, I think the issue is that the MATCHER argument
still filters out done states.
next prev parent reply other threads:[~2020-06-16 5:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-13 14:40 Stig Brautaset
2020-06-13 16:19 ` Stig Brautaset
2020-06-15 3:16 ` Kyle Meyer
2020-06-15 18:52 ` Stig Brautaset
2020-06-16 5:11 ` Kyle Meyer [this message]
2020-06-16 8:31 ` Stig Brautaset
2020-09-05 15:03 ` Bastien
2020-09-05 20:06 ` Stig Brautaset
2020-09-06 5:04 ` Bastien
2020-09-06 5:07 ` tags-todo agenda shoud not ignore DONE items (was: tags-todo org-agenda-custom-command weirdness) Bastien
2021-05-16 22:56 ` tags-todo agenda shoud not ignore DONE items Bastien
2021-05-17 4:46 ` Kyle Meyer
2021-05-17 5:24 ` Bastien
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).