nvim-orgmode / nvim-orgmode/orgmode

Implement tag hierarchy from core emacs-orgmode

Open
#998 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Lua
Stars
3.9k
Forks
190
Avg merge
2d 13h
Merged PRs (30d)
7

Description

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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. Start by locating the existing tag configuration and tagging/filtering implementation, then compare its behavior with Emacs Org's Tag Hierarchy documentation; the work is done when users can define parent and child tags and hierarchy-aware filtering behaves as documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
lua
Domain
developer-experience
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.