https://github.com/tbabej/taskwarrior-tag_expire-hook
An on-launch hook to expire (status:deleted) any task with an +expire hook, that is past due
https://github.com/tbabej/taskwarrior-tag_expire-hook
Last synced: 3 months ago
JSON representation
An on-launch hook to expire (status:deleted) any task with an +expire hook, that is past due
- Host: GitHub
- URL: https://github.com/tbabej/taskwarrior-tag_expire-hook
- Owner: tbabej
- Created: 2015-01-26T17:20:09.000Z (over 11 years ago)
- Default Branch: master
- Last Pushed: 2015-01-26T17:27:04.000Z (over 11 years ago)
- Last Synced: 2025-09-27T10:54:07.913Z (10 months ago)
- Language: Python
- Homepage:
- Size: 106 KB
- Stars: 3
- Watchers: 1
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# taskwarrior-tag_expire-hook
This taskwarrior hook-script is intended to
- get my feet wet, learning how hook-scripts work, starting with a basic one
- to offer users an easy alternative to assigning an until:date value, that is immediately after the due:date, for those tasks that are un-completable beyond the due:date.
By assigning a (user configurable) +expire tag, a task will be automatically and silently (?) deleted. This is desirable for high-frequncy, or daily tasks, like taking your vitamins. You don't need an overdue reminder to take yesterdays vitamins. If you took them yesterday, and marked the task completed, or you didn't, and today it was automatically deleted, you still have a decent record of hits and misses.
Possible advantages over using the until:date attribute
- speed of entry, "+expire" (could even be "+x") as opposed to until:date(due:date+1)
- does not rely on recurring tasks until:value shifting with due:value
- tags are visible in most reports, unlike until:attribute