taskwarrior: `project.not:side-quest or urgency>5` no longer working in 3.0.2 for context definition
I had:
context.default.read=project.not:side-quest or urgency>5
For my default context, and after upgrading to 3.0.2 (haven’t tested 3.0.0/1) it no longer works, how can I use the urgency filter again?
I also tried:
context.default.read="project.not:side-quest or urgency>5"
And it did not work either
More testing:
task list "project.not:side-quest or urgency>5"
Does not work
but
task list "urgency>5"
and
task list "project.not:side-quest"
Work well when used in isolation.
Funniest thing is
priority:H or +next or urgency>5
This works perfectly fine, so I have no clue what’s causing it not to work, is it project.not or a project with a - ?
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 21 (8 by maintainers)
https://github.com/GothenburgBitFactory/taskwarrior/issues/3440#issuecomment-2109119812 was reproduced in bash.
Me too 😃
Huh, I am wrong:
It looks like it’s doing a prefix match, which is to say,
project.not:foosays “projectdoes not begin withfoo”That said, I can replicate what you are seeing even with 2.6.2:
Task 88 has an urgency of 3.9. It does not appear in
task project.not:side-questnortask "urgency>5".To be honest, I have no idea how the filtering works in Taskwarrior, so I’m not sure how much more help I can be.