Civet has and and or, but currently no not. It does have not in, not instanceof, etc., and not is now reserved.

It's probably time to add a not operator as shorthand for !.

@STRd6 wanted this to have different precedence than coffeeNot. Is it that not x == y parses as not (x == y) as in Python, as compared to (not x) == y in CoffeeScript? How should not x or y parse? I would guess (not x) or y. Trying to figure out the general rule...