From mboxrd@z Thu Jan  1 00:00:00 1970
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Re: Bug? Group tags not working properly with agenda searches
Date: Thu, 08 Nov 2018 18:23:46 +0100
Message-ID: <87tvkrcwkd.fsf@nicolasgoaziou.fr>
References: <CAL2jp55xpfAm9pp31t6yWS0M6GnVYXpFkE99CyL+WEKtmvUr4g@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:58476)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mail@nicolasgoaziou.fr>) id 1gKo28-0003cX-La
	for emacs-orgmode@gnu.org; Thu, 08 Nov 2018 12:23:57 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <mail@nicolasgoaziou.fr>) id 1gKo24-0002xK-Ev
	for emacs-orgmode@gnu.org; Thu, 08 Nov 2018 12:23:56 -0500
Received: from relay1-d.mail.gandi.net ([217.70.183.193]:44235)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <mail@nicolasgoaziou.fr>)
	id 1gKo24-0002sa-8B
	for emacs-orgmode@gnu.org; Thu, 08 Nov 2018 12:23:52 -0500
In-Reply-To: <CAL2jp55xpfAm9pp31t6yWS0M6GnVYXpFkE99CyL+WEKtmvUr4g@mail.gmail.com>
	(Omari Norman's message of "Fri, 26 Oct 2018 17:04:42 -0400")
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode/>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: "Emacs-orgmode"
	<emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
To: Omari Norman <omari@smileystation.com>
Cc: emacs-orgmode@gnu.org

Hello,

Omari Norman <omari@smileystation.com> 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