Not sure if this is a bug or just “not a feature” but if the latter, it should probably warn you if you try to do it.
If you try to OR two negation filter terms, it ignores the OR and treats it like an AND. For example -is:star OR -pri:high is the same as -is:star -pri:high.
I was going to mention this in the other thread debating how the filter algorithm works, as it does reinforce the suggestion that negation, or exclude, terms are extracted and applied separately from the include terms. But as a practical matter to a user, it is a behavior that should implemented or the user should be warned.
