Closed linuxcaffe closed 8 years ago
@linuxcaffe I like the idea of supporting different file extensions and it turned out to be quite easy to implement. You can find the changes and an example in the taskopenrc.5 manpage on the devel branch (6eebc0a3308ca797e948aa8d26583353551adb42).
This is actually released now with v1.1.2.
That's great Johannes, thanks! I'm delighted to see continued development of taskopen, and I'm gonna file some other tasknotes refinements as separate issues. Go team!
Tasknotes (text files connected to a specific task by UUID naming convention) have some strengths and some weaknesses.
Strengths; they are more flexible than annotations.
Weaknesses;
In working last year on another task-related project (https://github.com/blakesweeney/unite-taskwarrior) which also has a tasknotes implementation, we came up with some effective answers;
File naming conventions
And secondly, on creation of a tasknote, unite-taskwarrior prepends the first line with a "* [ ] " and writes the task description, and appends the UUID.short (like #22cacc3b) so the first line of a tasknote includes a description of the task it is related to, and (bonus) it is also taskwiki-compliant, so that from within the tasknote, the task itself can be acted upon in several ways. That first line might look like;
* [ ] call Gordo about redheads #02275a77
(the two spaces between the description, and the "#" are important)
With these changes, tasknotes become more useful, and imho taskopen's implementation of tasknote functionality would benefit from their adoption.
thanks :)