Implement tag hierarchy from core emacs-orgmode

[codingvivi]

Does this feature exist in Emacs orgmode core?

Yes

Orgmode link

https://orgmode.org/manual/Tag-Hierarchy.html

Feature value

Additional context

The feature is pretty self explanatory and it is a part of core emacs.

(setq org-tag-alist '((:startgrouptag)
                      ("GTD")
                      (:grouptags)
                      ("Control")
                      ("Persp")
                      (:endgrouptag)
                      (:startgrouptag)
                      ("Control")
                      (:grouptags)
                      ("Context")
                      ("Task")
                      (:endgrouptag)))

The way it's implemented in emacs settings is kinda cumbersome though, having to these delimiters and calling out tags youve already defined is not only a bit of a pain, but the resulting settings file also isn't the most readable. If this structure is hard to implement or something and you cant be emacs lore accurate anyway, it might be more elegant to have each tag defined by the user in the plugin settings either be a string that represents the tag or a pair consisting of the tag and it's children or something. Either way the tagging/filtering this feature allows for is pretty powerful so it would be really cool if this was added in whatever way :)

Hope this wasn't suggested yet or is already possible or something. I've searched the documentation, the default settings and the issues and couldn't find it, but maybe I've just missed it somehow

[seflue]

Sounds like a useful feature. Wasn't aware, that this is in the Org spec, but I think, that could be configured easier with nested lua tables. Something like this:

{ 
  ["org-tag-alist"] = {
    {
      tag = "GTD",
      children = {
        "Control",
        "Persp"
      }
    },
    {
      tag = "Control",
      children = {
        "Context",
        "Task"
      }
    }
  }
}

This is simple to parse and clear to read. You could also use tuples of string and table with children, that would be even more compact - but this would be a bit harder to parse though I guess:

{
  ["org-tag-alist"] = {
    {"GTD", {
      "Control",
      "Persp"
    }},
    {"Control", {
      "Context",
      "Task"
    }}
  }
}