Yeah, so the current search filters doesn’t allow arbitrary AND/OR nesting, and parenthesis doesn’t work.
The way the search parsing currently works is
- The entire term is split by “OR” conditions
- Each part is split by the space character, and the AND operator is implicitly applied to them
So for example, “#work #due OR until:now” is parsed as:
- [#work #due] OR [until:now]
- [(#work) AND (#due)] OR [until:now]
But yeah, the OR operator currently only works on the outer-most level and cannot be nested.