S. Alspaugh

Warnings printed out when parsetabs created need to be addressed.

1

When the parsetabs are created you might notice warnings like: WARNING: 53 shift/reduce conflicts WARNING: Token 'OUTPUTNEW' defined, but not used WARNING: Token 'ASUC' defined, but not used WARNING: Token...

Self-explanatory.

Otherwise this is a possible bug.

See LexError for example of field you might need to print.

Also add an option to run_tests.py to exclude unimplemented commands.

The output of the search command when there is an argument like key=value is sometimes: ('EQ')     ('KEY')     ('VALUE') and other times: ('KEY')     ('VALUE') This should be consistent across commands.

Self-explanatory from title.

A recent policy is that when parsing queries that do not match the documentation, we still continue to "accept" them by having a valid parser rule for them (within reason...