Jorge <jorge13...@gmail.com> writes:
> [[info:org#Tag hierarchy]] says:
>
>> Furthermore; The members of a _group tag_ can also be regular
>> expression, creating the possibility of more dynamic and rule-based
>> tag-structure. The regular expressions in the group must be marked up
>> within { }. Example use, to expand on the example given above:
>>
>> #+TAGS: [ Vision : {V.+} ]
>> #+TAGS: [ Goal : {G.+} ]
>> #+TAGS: [ AOF : {AOF.+} ]
>> #+TAGS: [ Project : {P.+} ]
>>
>> Searching for the tag `Project' will now list all tags also including
>> regular expression matches for `P@.+'. Similar for tag-searches on
>> `Vision', `Goal' and `AOF'. This can be good for example if tags for a
>> certain project is tagged with a common project-identifier, i.e.
>> `P@2014_OrgTags'.
>
> However, the `Project' group tag regex is `P.+', while the first
> sentence in the final quoted paragraph cites the regex `P@.+' (with an
> `@').
>
> Emacs : GNU Emacs 25.0.92.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.18.6)
> of 2016-03-05
> Package: Org-mode version 8.3.4 (8.3.4-34-gacfd41-elpa @
> /home/jorge/.emacs.d/elpa/org-20160411/)
>
> I run Ubuntu 15.10 with PPAs gnome3-team/gnome3 and
> gnome3-team/gnome3-staging.
This was added with commit ecfd00cd by Gustav Wikström (cc'ed).
The paragraph is in need of some editing, but I think some of the @ signs are
wrong: they are used as escapes in the texi file and a couple of them
are missing. I attach a patch but it could use some review to make sure
it's correct.
>From 5d151cf4c5ddf779469e3bf860a0de85b3b771d8 Mon Sep 17 00:00:00 2001
From: Nick Dokos <ndo...@redhat.com>
Date: Mon, 11 Apr 2016 15:23:12 -0400
Subject: [PATCH] Fix the paragraph on tag groups as regular expressions.
Reword the paragraph and fix the regexps to include
the requisite @ signs.
---
doc/org.texi | 23 +++++++++++------------
1 file changed, 11 insertions(+), 12 deletions(-)
diff --git a/doc/org.texi b/doc/org.texi
index f935692..eb416d6 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -5200,23 +5200,22 @@ When setting @code{org-tag-alist} you can use @code{:startgroup} &
@code{:endgroup} instead of @code{:startgrouptag} & @code{:endgrouptag} to
make the tags mutually exclusive.
-Furthermore; The members of a @emph{group tag} can also be regular
-expression, creating the possibility of more dynamic and rule-based
-tag-structure. The regular expressions in the group must be marked up within
-@{ @}. Example use, to expand on the example given above:
+Furthermore, the members of a @emph{group tag} can also be regular
+expressions, creating the possibility of a more dynamic and rule-based
+tag structure. The regular expressions in the group must be specified
+within @{ @}. Here is an expanded example:
@example
-#+TAGS: [ Vision : @{V@.+@} ]
-#+TAGS: [ Goal : @{G@.+@} ]
-#+TAGS: [ AOF : @{AOF@.+@} ]
-#+TAGS: [ Project : @{P@.+@} ]
+#+TAGS: [ Vision : @{V@@@.+@} ]
+#+TAGS: [ Goal : @{G@@@.+@} ]
+#+TAGS: [ AOF : @{AOF@@@.+@} ]
+#+TAGS: [ Project : @{P@@@.+@} ]
@end example
Searching for the tag @samp{Project} will now list all tags also including
-regular expression matches for @samp{P@@.+}. Similar for tag-searches on
-@samp{Vision}, @samp{Goal} and @samp{AOF}. This can be good for example if
-tags for a certain project is tagged with a common project-identifier,
-i.e. @samp{P@@2014_OrgTags}.
+regular expression matches for @samp{P@@@.+}, and similarly for tag searches on
+@samp{Vision}, @samp{Goal} and @samp{AOF}. For example, this would work well
+for a project tagged with a common project-identifier, e.g. @samp{P@@2014_OrgTags}.
@kindex C-c C-x q
@vindex org-group-tags
--
2.7.0
--
Nick
