Menu

#78 Store additional todo.txt variables as attributes

none
open
None
False
Feature
2026-04-12
2026-04-12
No

Hi Henk. Long time user, first time feature requester. Love gtdsync - so thanks for everything!

Recently I've been using sleek to edit my todo.txt file: https://github.com/ransome1/sleek/wiki - it supports a few additional todo.txt variables: pm: # (pomodoro count), as well as pri:A-Z (archiving the (A)(B) etc. priority of tasks after completion). Would it be possible to have gtdsync store these additional variables as node attributes?

I also tend to lose +project context for my 'complete' tasks since in my workflow, when I complete tasks, I move the node from its project node context to a generic 'done' node to keep things visually manageable. Perhaps when gtdsync marks a task 'complete' it could also add a node attribute with the project name?

For future-proofing, perhaps it would make sense to have user-configurable additional todo.txt variables configured in the map - so people can extend the todo.txt syntax and have those variables retained as attributes by gdtsync?

Sorry if this is far-fetched - and thanks again for your amazing work on this!

Discussion


Log in to post a comment.

MongoDB Logo MongoDB