(NOT name:+) AND (NOT list:Sent)
The 2 searches:
1) NOT name:+ AND NOT list:Sent
2) (NOT name:+) AND (NOT list:Sent)
don't return the same result? Strange!
The other way around it doesn't matter:
3) NOT list:Sent AND NOT name:+
4) (NOT list:Sent) AND (NOT name:+)
give the same, correct, result.
Nr 1) above returns tasks that it shouldn't, the rest are OK.
I have had some problems before with NOT at the end of searches, can't remember the exact search though.
1) NOT name:+ AND NOT list:Sent
2) (NOT name:+) AND (NOT list:Sent)
don't return the same result? Strange!
The other way around it doesn't matter:
3) NOT list:Sent AND NOT name:+
4) (NOT list:Sent) AND (NOT name:+)
give the same, correct, result.
Nr 1) above returns tasks that it shouldn't, the rest are OK.
I have had some problems before with NOT at the end of searches, can't remember the exact search though.
annv says:
I thought you don't have to use 'AND' in front of NOT.
So just say:
NOT name:+ NOT list:Sent
So just say:
NOT name:+ NOT list:Sent
Correct, however i like the extra AND. Just to test it though, I removed the AND in all the above expressions and got the same result.
Actually, 3) above doesn't give the correct result either, showing tasks named "+XXX" when these should be removed. 1) returns tasks from Sent.
The reason for my interest is that when adding tasks directly to smart lists, the task inherits the properties of the smart list if they are unambiguous. Adding parantesis to the smart list filter is unfortunately a good way to confuse RTM, resulting in tasks that have no properties and, as a bonus feature, they immediately disappear. Hence I try to avoid () if possible.
Actually, 3) above doesn't give the correct result either, showing tasks named "+XXX" when these should be removed. 1) returns tasks from Sent.
The reason for my interest is that when adding tasks directly to smart lists, the task inherits the properties of the smart list if they are unambiguous. Adding parantesis to the smart list filter is unfortunately a good way to confuse RTM, resulting in tasks that have no properties and, as a bonus feature, they immediately disappear. Hence I try to avoid () if possible.
emily (Remember The Milk) says:
rajjan, I'm not sure of the reason for the different results -- I'll have to check with our engineer and find out.
With brackets or without, if there's a NOT anywhere in the expression, unfortunately this makes it ambiguous so it can't inherit the properties.
Hope this helps!
With brackets or without, if there's a NOT anywhere in the expression, unfortunately this makes it ambiguous so it can't inherit the properties.
Hope this helps!
emily (Remember The Milk) says:
We've just made some changes on our end, so "NOT" searches with and without brackets will both give the same result. If you continue to experience problems, please let me know. Thanks!