You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Related to #18 - I often keep a lot of notes in the markdown section for each task, however once it is marked as completed, I don't have an easy way to open a task's notes back up.
Current experience
I grep through resolved tasks to find the filename and open it.
Once opened, the task notes could be YAML-encoded, so I can't read them without decoding them separately
This makes for a painful experience - one that could be easy to solve, and a useful feature for others.
The text was updated successfully, but these errors were encountered:
I'm also thinking about how to handle notes that have a lifetime (or scope) beyond the lifetime/scope of a task.
The alternative solution to consider for such cases would be to have a separate notes system (e.g. vimwiki) and them somehow embed tasks within those, but then of course the question becomes how do we integrate that in/with dstask.
I was also thinking tasks could be full markdown files - YAML up top and markdown for the rest (the notes section). It follows the well-trodden path of static site generators (could use something like docsify to search/browse tasks and notes) however it would mean a file format change in dstask. That could get messy.
Referencing old tasks/notes via the CLI with part of the UUID would be fantastic though.
I was also thinking tasks could be full markdown files - YAML up top and markdown for the rest (the notes section). It follows the well-trodden path of static site generators (could use something like docsify to search/browse tasks and notes) however it would mean a file format change in dstask. That could get messy.
this sounds like a slightly different implementation, but not fundamentally different where it has a real impact.
Related to #18 - I often keep a lot of notes in the markdown section for each task, however once it is marked as completed, I don't have an easy way to open a task's notes back up.
Current experience
This makes for a painful experience - one that could be easy to solve, and a useful feature for others.
The text was updated successfully, but these errors were encountered: