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
Create two hooks to track the duration a task was active. Both hooks should be written in Python 3 and will require a Taskwarrior version >=2.4.
With totalactivetime UDA
The first hook should make use of a new UDA called totalactivetime of type duration which stores the total time in seconds. Every time a task gets stopped the value gets added to the old value. To simplify the communication with the Taskwarrior Hook v2 API the hook should make use of the taskw package which provides the bindings for Python. Note: This requires taskw as a direct dependency and must be installed on the target system! The package is available from the AUR.
Create two hooks to track the duration a task was active. Both hooks should be written in Python 3 and will require a Taskwarrior version
>=2.4
.With
totalactivetime
UDAThe first hook should make use of a new UDA called
totalactivetime
of typeduration
which stores the total time in seconds. Every time a task gets stopped the value gets added to the old value. To simplify the communication with the Taskwarrior Hook v2 API the hook should make use of the taskw package which provides the bindings for Python.Note: This requires taskw as a direct dependency and must be installed on the target system! The package is available from the AUR.
Taskwarrior integration
The second hook should be a fort from the official Taskwarrior
on-modify.taskwarrior
hook. It comes bundled with Taskwarrior, but can not be used via symlink, because the file is owned by theroot
user which prevents the script from being executed when symlinked.The usage of the hook is also documented in the official Timewarrior docs.
The text was updated successfully, but these errors were encountered: