Christian Moe writes:
> Right, thanks. I take it that there have to be spaces around the curly
> braces too, since the above doesn't work either, but
>
> #+TAGS: { rock : acdc cure } { pop : abba madonna }
> ^^^^^^
>
> works fine.
>
> Out of curiosity, I tried the chainin
Hi,
Bastien writes:
>> As a "Drupal taxonomy" fan, I think it would be even cooler to get a
>> multi-level tag tree by nesting groups
> Well, let's first see how useful is the current feature.
Fair enough.
> Your #+TAGS line does not match the correct syntax.
>
> #+TAGS: {rock : acdc cure} {
Hi Christian,
Christian Moe writes:
> As a "Drupal taxonomy" fan, I think it would be even cooler to get a
> multi-level tag tree by nesting groups, e.g.
>
> #+TAGS: { music : { rock : acdc cure } { pop : abba madonna } }
>
> which currently does nothing;
Well, let's first see how useful is
Bastien writes:
> This is now fixed in master.
Tested and confirmed!
> Glad you like the feature!
I've been looking forward to it for a while.
As a "Drupal taxonomy" fan, I think it would be even cooler to get a
multi-level tag tree by nesting groups, e.g.
#+TAGS: { music : { rock : acdc cu
Hi Christian,
Christian Moe writes:
> 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.
Thanks for testing this and for this detailed bug report.
This is now fixed in master.
Glad you like the featur
Hi,
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
