-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hook Error: Expected feedback from failing hook script (when using $XDG) #16
Comments
@kaushikgopal I think the problem here is that you're |
Note that XDG settings should be unrelated to this. The problem under the hood is slight CLI semantics change for |
ahh.. that might be it. interestingly, my setup script had this for installation:
I think I used your version of |
Got it. Those were indeed the official instructions at some point (when the official tasklib was not maintained frequently enough for me to be able to get my improvements in). Since then, several releases have been made, and the tasklib project was transferred over to GothenburgBitFactory org, so now I can make releases as well, ensuring the things are properly up to date. TL;DR: That line can be replaced by just using the official tasklib release on PYPI 🙂 |
I'm actually not entirely sure this is a task pirate issue (could actually just be a hooks + taskwarrior in general problem), but starting with an issue here, will move over to the right tool if folks have more input.
I recently moved to using XDG based directory structure for task warrior. I did this after upgrading to
2.6.1
.I notice this error happens only after one of my hooks (in this case the shift recurrence one) attempt to execute.
Some noteworthy environment variables:
Another peculiar observation is that there were
.data
files being created in my~/.config/task/
directoryLet me know if I can provide any more information or if I should instead open these in the main taskwarrior project.
The text was updated successfully, but these errors were encountered: