thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.23_rc0 2016-09-24T13:08:45Z 2016-09-24T13:08:45Z David Bremner david@tethera.net 2016-09-23T09:33:19Z urn:sha1:514a0a6a3bd74c03db6cd9b28edc0a29a8a2441e This is needed so that when the map is modified during traversal, and thus unlinked by the database code, the map is not disposed of until the iterator is done with it. 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:25Z David Bremner david@tethera.net 2016-06-13T01:05:52Z urn:sha1:58fe8fce1d1b7b86b4914a5a476ff21411c84082 This is a thin wrapper around the string map iterator API just introduced. 2016-09-21T21:14:24Z David Bremner david@tethera.net 2016-06-13T01:05:51Z urn:sha1:b846bdb48233c907d1ecaff495fbf6bc578910d6 Support for prefix based iterators is perhaps overengineering, but I wanted to mimic the existing database_config API. 2016-09-21T21:14:24Z David Bremner david@tethera.net 2016-06-13T01:05:50Z urn:sha1:b8bb6d796458732622f80464dd808b3e02f57d9d Initially, support get, set and removal of single key/value pair, as well as removing all properties. 2016-09-21T21:14:24Z David Bremner david@tethera.net 2016-06-13T01:05:49Z urn:sha1:8b03ee1d5a310f82718281362d105ff09e30148f The choice of array implementation is deliberate, for future iterator support 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-23T23:58:46Z David Bremner david@tethera.net 2016-06-27T20:43:04Z urn:sha1:59fed50a82b0a625a7303099675484557fed9d23 Without this change, the following code fails notmuch_directory_set_mtime(dir, 12345); assert(notmuch_directory_get_mtime(dir) == 12345); 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.