emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: Stig Brautaset <stig@brautaset.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: tags-todo org-agenda-custom-command weirdness
Date: Mon, 15 Jun 2020 03:16:07 +0000	[thread overview]
Message-ID: <87d061auiw.fsf@kyleam.com> (raw)
In-Reply-To: <m2ftazm3l1.fsf@brautaset.org>

Stig Brautaset writes:

> I'm seeing some weirdness with tags-todo vs tags custom agenda commands.
> Below is the smallest case I've managed to narrow it down to. I would
> *expect* that all the a1-4 commands return the same results, and that
> the b1-4 return the same results. That is not what I'm seeing, however.
> (setq-default org-agenda-custom-commands
>             '(("a1" "A1" tags-todo "-PROJ/TODO")
>               ("a2" "A2" tags "-PROJ/TODO")
>               ("a3" "A3" ((tags-todo "-PROJ/TODO")))
>               ("a4" "A4" ((tags "-PROJ/TODO")))
>               ("b1" "B1" tags-todo "-PROJ/DONE")
>               ("b2" "B2" tags "-PROJ/DONE")
>               ("b3" "B3" ((tags-todo "-PROJ/DONE")))
>               ("b4" "B4" ((tags "-PROJ/DONE")))))

I agree with your expectation that a1-4 should be the same.  Why do you
expect that b1-4 would be?  Shouldn't tags-todo consider only none-DONE
todo items, in the same spirit as m versus M?  In other words, I'd
expect b1 and b3 to be empty by definition.

> The effect of a1 & a2 appears identical to eachother, and a3 & a4 too,
> but a1-2 and a3-4 differ (in that the former seems to include scheduled
> items, but the latter does not.)

It's helpful if you provide a minimal test file.  I've tried to come up
with one that I think should capture what you're describing.

--8<---------------cut here---------------start------------->8---
* TODO h1                                                               :PROJ:
* TODO h2
* DONE h3                                                               :PROJ:
* DONE h4
* TODO h5                                                               :PROJ:
SCHEDULED: <2020-06-14 Sun>
* TODO h6
SCHEDULED: <2020-06-14 Sun>
* DONE h7                                                               :PROJ:
SCHEDULED: <2020-06-14 Sun>
* DONE h8
SCHEDULED: <2020-06-14 Sun>
--8<---------------cut here---------------end--------------->8---

With that, a1-4 all show:

    scratch:    TODO h2
    scratch:    TODO h6

That doesn't match what you're seeing.  I'm testing with 706970 checked
out, the commit you reported in your follow-up message.

> What I'm seeing for b1-4 is even weirder. Here I observe b1, b2 and b4
> have identical behaviour[*], but b3 is the odd one out: while the other
> three return a list of DONE non-project tasks, b3 doesn't find anything.
> [*] I suspect the reason b2 and b4 are identical is that I have no
> scheduled DONE tasks.

For b2 and b4, I see

    scratch:    DONE h4
    scratch:    DONE h8

b1 and b3 are empty, which I think is expected given the tags-todo type.

  parent reply	other threads:[~2020-06-15  3:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-13 14:40 tags-todo org-agenda-custom-command weirdness Stig Brautaset
2020-06-13 16:19 ` Stig Brautaset
2020-06-15  3:16 ` Kyle Meyer [this message]
2020-06-15 18:52   ` Stig Brautaset
2020-06-16  5:11     ` Kyle Meyer
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

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:

  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=87d061auiw.fsf@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=stig@brautaset.org \


* 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).