search

PiRSquared17 / bpbible

Automatically exported from code.google.com/p/bpbible
Other
0 stars 1 forks source link

Searching throws parsing errors: More search operators needed #81

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
If you enter a badly formed search query, a nasty ParseError is displayed,
suggesting that the program has crashed or something has gone wrong.  This
should produce a nicer error, preferably linking to the search instructions
or giving helpful suggestions.

I think our search syntax should include a little more.  For example
(Jesus|Christ) and (Jesus OR Christ) will both give parsing errors, and I
can never remember the "correct" (Jesus, Christ).  Both "or" and "and" (and
probably "not" as well) should behave as operators rather than as words to
search for (if people want to actually search for those words they should
search for "+and" or "+or").  This will make it much closer to what people
expect.

Original issue reported on code.google.com by jonmmor...@gmail.com on 30 Jun 2009 at 12:18

GoogleCodeExporter commented 9 years ago 
Proportional spacing means you can no longer see where the error in parsing 
occurred.
 I'm not sure that most users will understand or want to understand this, but it
would be nice to preserve it if we can.

Original comment by jonmmor...@gmail.com on 7 Jul 2009 at 12:37