 | wohler says:If I have a smart list, say tag:call, and create a new task, it inherits the "call" tag. If the smart list is modified to say,'tag:call dueWithin:"two weeks of today"', new tasks still inherit the "call" tag. So far, so good.
Now modify the list criteria to 'tag:call not dueAfter:"two weeks of today"', new tasks do *not* inherit the "call" tag. They should!
Brendan points out that the "not dueAfter" introduces an ambiguity. Just because the date is ambiguous doesn't mean that all properties can't be inherited. Given the example above, only the due date is ambiguous. The tag will always be "call" and can be applied to new tasks as whibs mentioned over three years ago!
This problem applies to most of my lists since the use of "not dueAfter" or "or dueBefore" are excellent, and likely common, ways of limiting the visibility of tasks to those that are due soon. As a result, I need to add two or three tags to every task I add instead of zero. And if I forget, I need to go searching in Inbox for it. Posted 1 year ago |