thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.23_rc0 2016-09-21T21:14:25Z 2016-09-21T21:14:25Z Daniel Kahn Gillmor dkg@fifthhorseman.net 2016-07-08T09:15:36Z urn:sha1:693ca8d8a80438ce1e361e7e6d22288f52a11c55 We want to be able to query the properties directly, like: notmuch count property:foo=bar which should return a count of messages where the property with key "foo" has value equal to "bar". 2016-09-21T21:14:24Z David Bremner david@tethera.net 2016-06-13T01:05:48Z urn:sha1:4dfb69169e6b685670ebdeedab898c31adc995b2 This is a first step towards providing an API to attach arbitrary (key,value) pairs to messages and retrieve all of the values for a given key. 2016-08-18T08:11:37Z David Bremner david@tethera.net 2016-08-18T08:06:54Z urn:sha1:9e177b236c7054bc6a51c4718bfd4b31cd4f8b20 I believe the current one is misleading, because in my experiments Xapian did not add : when prefix and term were both upper case. Indeed, it's hard to see how it could, because prefixes are added at a layer above Xapian in our code. See _notmuch_message_add_term for an example. Also try to explain why this is a good idea. As far as I can ascertain, this is more of an issue for a system trying to work with an unknown set of prefixes. Since notmuch has a fixed set of prefixes, and we can hopefully be trusted not to add XGOLD and XGOLDEN as prefixes, it is harder for problems to arise. 2016-08-09T00:34:11Z David Bremner david@tethera.net 2016-07-15T10:25:41Z urn:sha1:293186d6c6b1c4d158413de5412e6b4345e94970 _notmuch_database_log clears the log buffer each time. Rather than introducing more complicated semantics about for this function, provide a second function that does not clear the buffer. This is mainly a convenience function for callers constructing complex or multi-line log messages. The changes to query.cc are to make sure that the common code path of the new function is tested. 2016-06-29T07:03:34Z Istvan Marko notmuch@kismala.com 2016-06-26T15:29:43Z urn:sha1:9b60dc3cd9224eddfe9bc5cf74eeaa5f0d599d04 Xapian 1.3 has introduced the DB_RETRY_LOCK flag (Xapian bug 275). Detect it in configure and optionally use it. With this flag commands that need the write lock will wait for their turn instead of aborting when it's not immediately available. Amended by db: allow disabling in configure 2016-06-10T12:20:22Z David Bremner david@tethera.net 2016-06-10T02:35:27Z urn:sha1:4291f326809692bad61b50f942dc366e59ab30ef The field processor objects need to be deallocated explicitly just like the range processors (or a talloc destructor defined). 2016-06-07T10:51:57Z David Bremner david@tethera.net 2016-06-04T22:17:41Z urn:sha1:ba0b95f846820b1d71f67731a8c38ac2866c921a This probably should have been part of 3458e3c89c, but I missed it. 2016-06-05T11:32:17Z Daniel Kahn Gillmor dkg@fifthhorseman.net 2016-06-02T16:26:14Z urn:sha1:6a833a6e83865f6999707cc30768d07e1351c2cb Many of the external links found in the notmuch source can be resolved using https instead of http. This changeset addresses as many as i could find, without touching the e-mail corpus or expected outputs found in tests. 2016-06-05T11:23:28Z Tomi Ollila tomi.ollila@iki.fi 2016-05-28T17:45:31Z urn:sha1:cf09631a45d276826255d197c1d5c913a29c79f4 Cleaned the following whitespace in lib/* files: lib/index.cc: 1 line: trailing whitespace lib/database.cc 5 lines: 8 spaces at the beginning of line lib/notmuch-private.h: 4 lines: 8 spaces at the beginning of line lib/message.cc: 1 line: trailing whitespace lib/sha1.c: 1 line: empty lines at the end of file lib/query.cc: 2 lines: 8 spaces at the beginning of line lib/gen-version-script.sh: 1 line: trailing whitespace 2016-05-25T10:40:44Z David Bremner david@tethera.net 2016-03-22T10:54:54Z urn:sha1:b9bf3f44eacd42ce53885c79f9dad8d82c76f13d This relies on the optional presense of xapian field processors, and the library config API.