Taskwarrior Chained Recurrence Hook
Painlessly adds chained recurrence to Taskwarrior. Requires Python >= 3.8.
In the illustration above, task 26ccff69 is automatically created when task
90e414dl is completed. With the new task having the equivalent due and
wait attributes, relative to it's own entry attribute.
It's common to have due or wait fall on a day boundary such as 23:59 or
00:00, this is usually because a named date such as eod or sod was used
when creating the original task. If this is the case, new tasks will be created
with the due and wait attributes automatically falling on the equivalent
day boundaries. If this sounds convoluted, the "Usage" section below
has a simple example.
Install
$ pip install chained-recurrence
$ chained-recurrence install
Usage
Create tasks as you usually would, adding chained:on:
$ task add chained:on 'hair cut'
When this task's status is changed to complete, a new one will be created.
The wait and due attributes can also be used, their date and time values
will be updated in relation to the current date and time:
$ date
Mon 1 Jan 18:00:00 GMT 2024
$ task add chained:on wait:1d 'workout'
Created task 1.
$ date
Sat 20 Jan 09:00:00 GMT 2024
$ task 1 done
Completed task ab566e0f 'workout'.
Completed 1 task.
Creating new chained task.
The newly created chained task will have the following:
| Attribute | Value |
|---|---|
| wait | 2024-01-21 09:00:00 |
Named Dates
$ date
Mon 1 Jan 18:00:00 GMT 2024
$ task add chained:on wait:sod+1d due:eod+2d 'workout'
Created task 1.
$ date
Sat 20 Jan 09:00:00 GMT 2024
$ task 1 done
Completed task ab566e0f 'workout'.
Completed 1 task.
Creating new chained task.
The newly created chained task will have the following:
| Attribute | Value |
|---|---|
| wait | 2024-01-21 00:00:00 |
| due | 2024-01-22 23:59:59 |
Uninstall
$ chained-recurrence uninstall
$ pip uninstall chained-recurrence
1 maintainer
Metadata
1 maintainer
Release files for chained-recurrence 0.0.13
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| chained-recurrence-0.0.13.tar.gz | 5.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| chained_recurrence-0.0.13-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 12.3 kB
Release files / chained-recurrence-0.0.13.tar.gz
| Download URL | chained-recurrence-0.0.13.tar.gz |
|---|---|
| Size | 5.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3ccc59141f365e4bc73022d5bdb896d0bf00550162629cd74c5a71214c83a886
|
|
BLAKE2b-256 checksum How to use checksums |
bdc93ca5528f3f132bb01e8901e93eb5b4967641d09fcea60e1975fe0ce52b31
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.3
|
Release files / chained_recurrence-0.0.13-py3-none-any.whl
| Download URL | chained_recurrence-0.0.13-py3-none-any.whl |
|---|---|
| Size | 6.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
125e211d183facc3d2338b1578eeff9a9d9b44d0bf770c47dca7105ed1081548
|
|
BLAKE2b-256 checksum How to use checksums |
9ffdccf0c4a14cda92ef28546643d1a134a985392eda052f53ef596d86c610db
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.3
|
Security for chained-recurrence 0.0.13
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
