libnotmuch should catch QueryParserError seperately.

classic Classic list List threaded Threaded
1 message Options
David Bremner-2 David Bremner-2
Reply | Threaded
Open this post in threaded view
|

libnotmuch should catch QueryParserError seperately.

Today I observed the following

% notmuch search crash+date:@1505185200..@1521169200000
notmuch search: A Xapian exception occurred
A Xapian exception occurred parsing query: Unknown range operation
Query string was: crash+date:@1505185200..@1521169200000

This is roughly OK for a command line user, but contains very little
information for bindings users; I originally found this string
attempting to debug nmweb.

I _think_ it should be possible to catch the more specific error
here. Since this is an error that is generated by user input, it seems
worthwhile trying to do a better job.

d


_______________________________________________
notmuch mailing list
[hidden email]
https://notmuchmail.org/mailman/listinfo/notmuch