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
I do not know what may be done or not about this, but I experience a naming conflict. go-task's task tool and taskwarrior's task tool share the same name.
I do not expect a renaming of either, but that name conflicts impacts me. I indeed use taskwarrior as a locally configured and locally set up bug tracker on my machine. Local to a git repo. I find it pretty much convenient. Until that name conflict.
I opened a bug report on Debian's Bug Tracking system.
This has been discussed at length in the past. There is not much that we or the maintainers of taskwarrior can do about this given that both tools are well established. The number of users that have both installed is fairly small and some basic knowledge of PATH and aliases can help to avoid conflicts - much like the tool you linked.
Hi.
I do not know what may be done or not about this, but I experience a naming conflict. go-task's task tool and taskwarrior's task tool share the same name.
I do not expect a renaming of either, but that name conflicts impacts me. I indeed use taskwarrior as a locally configured and locally set up bug tracker on my machine. Local to a git repo. I find it pretty much convenient. Until that name conflict.
I opened a bug report on Debian's Bug Tracking system.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071939
And on taskwarrior's github repos:
GothenburgBitFactory/taskwarrior#3463
GothenburgBitFactory/taskshell#75
Anyway...
Good luck with your task runner development.
Best.
The text was updated successfully, but these errors were encountered: