mirror of
https://git.notmuchmail.org/git/notmuch
synced 2024-11-25 04:18:08 +01:00
9c5ea07cc6
The JSON format eliminates the complex escaping issues that have plagued the text search format. This uses the incremental JSON parser so that, like the text parser, it can output search results incrementally. This slows down the parser by about ~4X, but puts us in a good position to optimize either by improving the JSON parser (evidence suggests this can reduce the overhead to ~40% over the text format) or by switching to S-expressions (evidence suggests this will more than double performance over the text parser). [1] This also fixes the incremental search parsing test. This has one minor side-effect on search result formatting. Previously, the date field was always padded to a fixed width of 12 characters because of how the text parser's regexp was written. The JSON format doesn't do this. We could pad it out in Emacs before formatting it, but, since all of the other fields are variable width, we instead fix notmuch-search-result-format to take the variable-width field and pad it out. For users who have customized this variable, we'll mention in the NEWS how to fix this slight format change. [1] id:"20110720205007.GB21316@mit.edu" |
||
---|---|---|
.. | ||
coolj.el | ||
Makefile | ||
Makefile.local | ||
notmuch-address.el | ||
notmuch-crypto.el | ||
notmuch-hello.el | ||
notmuch-lib.el | ||
notmuch-logo.png | ||
notmuch-maildir-fcc.el | ||
notmuch-message.el | ||
notmuch-mua.el | ||
notmuch-print.el | ||
notmuch-query.el | ||
notmuch-show.el | ||
notmuch-tag.el | ||
notmuch-wash.el | ||
notmuch.el |