thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.20 2015-04-08T14:43:55Z 2015-04-08T14:43:55Z David Bremner david@tethera.net 2015-04-07T12:10:15Z urn:sha1:294bb6de20de7d9c83a45dca22888d557ece588a Apparently some systems actually have a directory called /nonexist[ae]nt. It's hard to fathom a good reason for that, but oh well. As long as we don't create such a directory inside the notmuch source tree, the new version should be more robust. 2015-04-08T14:43:55Z David Bremner david@tethera.net 2015-04-08T14:31:43Z urn:sha1:2e9ecb611a7f698808add756b2ddcbdfcd8b7c8b Apparently most of the misspellings are my fault. 2015-03-29T07:50:01Z David Bremner david@tethera.net 2015-03-29T07:39:46Z urn:sha1:703c8f9511c6f96023fb180b0e9d831e762befc9 Since notmuch_database_status_string can return NULL, passing it directly to fputs is not a good idea. 2015-03-28T23:34:15Z David Bremner david@tethera.net 2015-03-28T23:24:38Z urn:sha1:6a99505625785022d490207bdf6e3e29ed156c6a This second half of the error reporting tests actually uses the function notmuch_database_status_string to retrieve the last logged error 2015-03-28T23:34:15Z David Bremner david@tethera.net 2014-12-26T16:25:35Z urn:sha1:736ac26407914425a9c94e86616225292cf716dd This is not supposed to change any functionality from an end user point of view. Note that it will eliminate some output to stderr. The query debugging output is left as is; it doesn't really fit with the current primitive logging model. The remaining "bad" fprintf will need an internal API change. 2015-03-28T23:34:15Z David Bremner david@tethera.net 2015-03-14T08:50:55Z urn:sha1:83298fa0f8e7717a260c1f88edd7bf545709562d This first half of the tests is all that don't need to retrieve the the error string explicitly from the notmuch database structure.