That’s as good a reason as any to keep your system in source control. I run scripts over my work fairly frequently. The ability to roll back if I find something didn’t work right is awesome.
I also recommend documenting the script or awk command in the commit message to make it easy to find later.
I have recently learned that in the next major release of Dataview (date uncertain) there will be support for multivalued task states. At that point I will be able to simplify Taskidian a lot, since I won't have to indicate task state like `- [ ] [ø:: !]` but instead `- [!]`. That will be much easier to use. I'll have to do a batch edit of tasks, and rewizzle my queries, but worth it.
That’s as good a reason as any to keep your system in source control. I run scripts over my work fairly frequently. The ability to roll back if I find something didn’t work right is awesome.
I also recommend documenting the script or awk command in the commit message to make it easy to find later.
Love this. I've been thinking of something like this for a while. Well done!
I have recently learned that in the next major release of Dataview (date uncertain) there will be support for multivalued task states. At that point I will be able to simplify Taskidian a lot, since I won't have to indicate task state like `- [ ] [ø:: !]` but instead `- [!]`. That will be much easier to use. I'll have to do a batch edit of tasks, and rewizzle my queries, but worth it.
This might be a preview of sorts:
https://minimal.guide/Block+types/Checklists