-
-
Notifications
You must be signed in to change notification settings - Fork 72
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
Context not working sometimes #556
Comments
I can guarantee that taskwarrior-tui doesn't interpret context as taskwarrior does, for instance:
Will work on taskwarrior-tui but fail on taskwarrior, and:
Will work on taskwarrior but fail on taskwarrior-tui. So I can either use one or the other, not both. |
When you say it fails in
You can look at the log files of Line 1714 in cfedca0
Maybe that'll help narrow down what is going on? I'm assuming it has something to do with how the context string is spliced into the subprocess when tasks are exported: Lines 1698 to 1706 in cfedca0
|
logging
Does not show me any logs unless they are somewhere I'm unfamiliar with. clarifying bug
I'm having some inconsistencies, over iterations(slightly modified context) I had 3 different results:
Using
|
I've ran into the same problem.
This small change made taskwarrior show only 'Task not found". Using the context with task works. The log is
I don't know if it helps anything, but copying these for python's subprocess, the one given by taskwarrior-tui fails with
|
Had time to test it
|
Reproduction
$ task
$ taskwarrior-tui
My context is
side-quest
could it be because of the "-"??The text was updated successfully, but these errors were encountered: