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
Refresh custom displays whenever a TaskLite command is run
Show messages from a message server after each task command
More Ideas
Support for hooks to be stored in the database in a scripting language which are then executed by TaskLite.
They could e.g. be written in Lua (https://hackage.haskell.org/package/hslua) or Nix (https://github.com/haskell-nix/hnix). (Dhall is unfortunately not ergonomic enough).
I always disliked the system for git hooks, in which they are not part of the project and everybody had to install them themselves.
It could then even be extended with custom functions.
This could lead to a collection of useful hook scripts that anyone can use, since they are executed by TaskLite and have no additional requirements for the system setup like installed interpreters and so on.
Use Nix as the basis for a TaskLite plugin manager
Similar to Taskwarrior's hooks: https://taskwarrior.org/docs/hooks_guide.html
Example use cases
~/.tasklite
folder with git on launch (pull from remote)and on exit (push to remote)
More Ideas
Support for hooks to be stored in the database in a scripting language which are then executed by TaskLite.
They could e.g. be written in Lua (https://hackage.haskell.org/package/hslua) or Nix (https://github.com/haskell-nix/hnix). (Dhall is unfortunately not ergonomic enough).
I always disliked the system for git hooks, in which they are not part of the project and everybody had to install them themselves.
It could then even be extended with custom functions.
This could lead to a collection of useful hook scripts that anyone can use, since they are executed by TaskLite and have no additional requirements for the system setup like installed interpreters and so on.
Use Nix as the basis for a TaskLite plugin manager
Tracking issue for @robwhitaker's request in #2 (comment)
The text was updated successfully, but these errors were encountered: