[O] Bug? Group tags not working properly with agenda searches

[Omari Norman]

Hello,

First of all, thank you for org-mode.  Without it, I literally would find
it much more difficult to do my job.

I am having a problem with group tags.  I reproduced it using the latest
org-mode from the org package archive, 20181022.  The minimal example is
this: say I have a group tag that looks like this:

(setq org-tag-alist
  '((:startgrouptag)
  ("parentTag")
  (:grouptags)
  ("childTag1")
  ("childTag2")
  (:endgrouptag)))

with a org-todo-keywords like so:

(setq org-todo-keywords '((type "TODO" "NEXT" "|" "DONE" "CANCELLED")))

And then an org file that looks like this:

* Parent heading 1 :childTag1:
** NEXT child 1 of parent 1
** TODO child 2 of parent 1

* Parent heading 2
** NEXT child 1 of parent 2
** TODO child 2 of parent 2

Then when I hit C-c a M, I use this match string:

parentTag&TODO="NEXT"|-parentTag&TODO="TODO"

I would expect the resulting agenda to have exactly two items: "child 1 of
parent 1", and "child 2 of parent 2".  However, I get three items: "child 1
of parent 1", "child 2 of parent 1", and "child 2 of parent 2".  I don't
understand why "child 2 of parent 1" is in there.

This only arises when using the "|" operator.  That is, if I do an agenda
with just

parentTag&TODO="NEXT"

then I get just "child 1 of parent 1", as expected.  If I do an agenda with

-parentTag&TODO="TODO"

then I get just "child 2 of parent 2", as expected.  But when I combine
them with "|", I get three items.

I also did some other tests showing that at least for me this problem
arises only with group tags.  In particular, here if I do

childTag1&TODO="NEXT"|-childTag1&TODO="TODO"

I get just the two items I would expect.

Is there a bug here?  Or am I doing something wrong?  Thanks.  --Omari

Re: [O] Bug? Group tags not working properly with agenda searches

[Omari Norman]

I tried the Org mode from the Org mode ELPA (org-20181112.tar) but
apparently the bug fix is not in there yet.  But I also tried the one from
the latest Git and it's fixed in there.  Thanks very much.  --Omari

On Thu, Nov 8, 2018 at 12:24 PM Nicolas Goaziou 
wrote:

> Hello,
>
> Omari Norman  writes:
>
> > I am having a problem with group tags.  I reproduced it using the latest
> > org-mode from the org package archive, 20181022.  The minimal example is
> > this: say I have a group tag that looks like this:
> >
> > (setq org-tag-alist
> >   '((:startgrouptag)
> >   ("parentTag")
> >   (:grouptags)
> >   ("childTag1")
> >   ("childTag2")
> >   (:endgrouptag)))
> >
> > with a org-todo-keywords like so:
> >
> > (setq org-todo-keywords '((type "TODO" "NEXT" "|" "DONE" "CANCELLED")))
> >
> > And then an org file that looks like this:
> >
> > * Parent heading 1 :childTag1:
> > ** NEXT child 1 of parent 1
> > ** TODO child 2 of parent 1
> >
> > * Parent heading 2
> > ** NEXT child 1 of parent 2
> > ** TODO child 2 of parent 2
> >
> > Then when I hit C-c a M, I use this match string:
> >
> > parentTag&TODO="NEXT"|-parentTag&TODO="TODO"
> >
> > I would expect the resulting agenda to have exactly two items: "child 1
> of
> > parent 1", and "child 2 of parent 2".  However, I get three items:
> "child 1
> > of parent 1", "child 2 of parent 1", and "child 2 of parent 2".  I don't
> > understand why "child 2 of parent 1" is in there.
> >
> > This only arises when using the "|" operator.  That is, if I do an agenda
> > with just
> >
> > parentTag&TODO="NEXT"
> >
> > then I get just "child 1 of parent 1", as expected.  If I do an agenda
> with
> >
> > -parentTag&TODO="TODO"
> >
> > then I get just "child 2 of parent 2", as expected.  But when I combine
> > them with "|", I get three items.
> >
> > I also did some other tests showing that at least for me this problem
> > arises only with group tags.  In particular, here if I do
> >
> > childTag1&TODO="NEXT"|-childTag1&TODO="TODO"
> >
> > I get just the two items I would expect.
> >
> > Is there a bug here?  Or am I doing something wrong?
>
> It was a bug, now hopefully fixed.
>
> Thank you.
>
> Regards,
>
> --
> Nicolas Goaziou
>

[O] Manual does not mention LEVEL special property

[Omari Norman]

Hi,

The Org mode manual does not mention the LEVEL special property; can you
please add it?

https://orgmode.org/manual/Special-properties.html

Thanks for all your work on Org mode!  --Omari