emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Christian Moe <mail@christianmoe.com>
To: Emacs-orgmode@gnu.org
Cc: Bastien <bzg@gnu.org>
Subject: [BUG?] New group tag feature matches too much
Date: Fri, 12 Apr 2013 10:29:16 +0200	[thread overview]
Message-ID: <m2vc7sup7n.fsf@christianmoe.com> (raw)


I was delighted to discover the new group tags feature in 8.0, but I'm
getting strange results trying it out with a sparse tree.

It looks like matching a group tag matches not only the subtags, but
also spuriously matches any tag that *contains* the string of a subtag. 

So when I match for the tag 'pop' in the below example, I get not only
Entry 5 which is tagged 'abba', but also Entry 7, tagged
'yabbadabbadoo'. A tag match for 'abba' correctly returns only Entry 5.

Example buffer:

#+TAGS: { a : aa ab } { rock : ac dc } { pop : abba }
* Entry 1 (grouptag) 							  :a:
* Entry 2 (with subtag) 					      :aa:bb:
* Entry 3 (no subtag) 						      :ac:dc:
* Entry 4 (with subtag) 					   :bb:ab:dd:
* Entry 5 (no subtag) 						 :bb:cc:abba:
* Entry 6 (no subtag, no 'a' character in tags) 		 :bb:dc:bbdb:
* Entry 7 (no subtag, 'abba' sequence in tag)		      :yabbadabbadoo:

* Some sparse tree results

Doing `C-c / m' with the following tags produces the following results:
- rock :: matches Entry 3 and 6, CORRECT
- a :: spurious match of every Entry except 6, the only one without any tag with
       an `a' character, WRONG
  - Expected: match Entry 1, 2, 4
- ab :: matches Entry 4, CORRECT
- abba :: matches Entry 5, CORRECT (no spurious match of Entry 7)
- pop :: matches Entry 5 and 7, WRONG (spurious match of Entry 7)


             reply	other threads:[~2013-04-12  8:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-12  8:29 Christian Moe [this message]
2013-04-12  8:46 ` [BUG?] New group tag feature matches too much Bastien
2013-04-12  9:45   ` Christian Moe
2013-04-12 10:21     ` Bastien
2013-04-12 13:07       ` Christian Moe
2013-04-12 17:23         ` 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=m2vc7sup7n.fsf@christianmoe.com \
    --to=mail@christianmoe.com \
    --cc=Emacs-orgmode@gnu.org \
    --cc=bzg@gnu.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).