From mboxrd@z Thu Jan 1 00:00:00 1970 From: Omari Norman Subject: Re: Bug? Group tags not working properly with agenda searches Date: Tue, 13 Nov 2018 22:41:31 -0500 Message-ID: References: <87tvkrcwkd.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="0000000000007bd475057a97b647" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:37729) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gMm3p-0005Kt-W6 for emacs-orgmode@gnu.org; Tue, 13 Nov 2018 22:41:51 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gMm3m-0005ZW-QU for emacs-orgmode@gnu.org; Tue, 13 Nov 2018 22:41:49 -0500 Received: from mail-lf1-f43.google.com ([209.85.167.43]:46181) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gMm3m-0005ZB-JN for emacs-orgmode@gnu.org; Tue, 13 Nov 2018 22:41:46 -0500 Received: by mail-lf1-f43.google.com with SMTP id f23so10463520lfc.13 for ; Tue, 13 Nov 2018 19:41:45 -0800 (PST) In-Reply-To: <87tvkrcwkd.fsf@nicolasgoaziou.fr> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode@gnu.org --0000000000007bd475057a97b647 Content-Type: text/plain; charset="UTF-8" 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 > --0000000000007bd475057a97b647 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I tried the Org mode from the Org mode ELPA (org-20181112.= tar) but apparently the bug fix is not in there yet.=C2=A0 But I also tried= the one from the latest Git and it's fixed in there.=C2=A0 Thanks very= much. =C2=A0--Omari

On= Thu, Nov 8, 2018 at 12:24 PM Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
Hello,

Omari Norman <omari@smileystation.com> writes:

> I am having a problem with group tags.=C2=A0 I reproduced it using the= latest
> org-mode from the org package archive, 20181022.=C2=A0 The minimal exa= mple is
> this: say I have a group tag that looks like this:
>
> (setq org-tag-alist
>=C2=A0 =C2=A0 =C2=A0 =C2=A0'((:startgrouptag)
>=C2=A0 =C2=A0 =C2=A0 =C2=A0("parentTag")
>=C2=A0 =C2=A0 =C2=A0 =C2=A0(:grouptags)
>=C2=A0 =C2=A0 =C2=A0 =C2=A0("childTag1")
>=C2=A0 =C2=A0 =C2=A0 =C2=A0("childTag2")
>=C2=A0 =C2=A0 =C2=A0 =C2=A0(: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=3D"NEXT"|-parentTag&TODO=3D"TODO= "
>
> I would expect the resulting agenda to have exactly two items: "c= hild 1 of
> parent 1", and "child 2 of parent 2".=C2=A0 However, I = get three items: "child 1
> of parent 1", "child 2 of parent 1", and "child 2 = of parent 2".=C2=A0 I don't
> understand why "child 2 of parent 1" is in there.
>
> This only arises when using the "|" operator.=C2=A0 That is,= if I do an agenda
> with just
>
> parentTag&TODO=3D"NEXT"
>
> then I get just "child 1 of parent 1", as expected.=C2=A0 If= I do an agenda with
>
> -parentTag&TODO=3D"TODO"
>
> then I get just "child 2 of parent 2", as expected.=C2=A0 Bu= t when I combine
> them with "|", I get three items.
>
> I also did some other tests showing that at least for me this problem<= br> > arises only with group tags.=C2=A0 In particular, here if I do
>
> childTag1&TODO=3D"NEXT"|-childTag1&TODO=3D"TODO= "
>
> I get just the two items I would expect.
>
> Is there a bug here?=C2=A0 Or am I doing something wrong?

It was a bug, now hopefully fixed.

Thank you.

Regards,

--
Nicolas Goaziou
--0000000000007bd475057a97b647--