aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-05-14 08:25:19 -0500
committerCraig Jennings <c@cjennings.net>2026-05-14 08:25:19 -0500
commit686d6471191888d05bcdd1f194a9d5dd5ee65d7a (patch)
treecc448527b706ff3ec66450b0d41bc57e27a69ce6 /docs
parentdb87d0793a04b88fa1347ca5259f537aa8838a79 (diff)
downloadrulesets-686d6471191888d05bcdd1f194a9d5dd5ee65d7a.tar.gz
rulesets-686d6471191888d05bcdd1f194a9d5dd5ee65d7a.zip
fix(todo-cleanup): read priority via org-heading-components, not regex
The first take walked the heading line with a plain `\[#\([A-Z]\)\]` regex, which matched any cookie-shaped substring anywhere in the line. Dated-log headings can carry that shape inside the title — e.g. "Reprioritized children =[#D]= → =[#B]= to match parent" quotes earlier and new priorities verbatim, and the script read =[#D]= as if it were the heading's own priority cookie. `(nth 3 (org-heading-components))` only returns a priority when the cookie sits in canonical position (right after the stars or the optional TODO keyword), which is the only place org itself recognizes it. That's the right primitive here. Surfaced via smoke-testing --check-child-priority against ~/projects/work/todo.org: 10 candidates dropped to 9 once the dated-log heading inside the Whisper parent stopped getting flagged. New ert test tc-sync-ignores-cookie-shaped-text-in-title covers the case directly.
Diffstat (limited to 'docs')
0 files changed, 0 insertions, 0 deletions