notmuch/lib/notmuch.h, branch 0.29.2 thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.29.2 2019-01-26T00:51:00Z docs: Use correct call to notmuch_query_search_threads in usage example 2019-01-26T00:51:00Z rhn gihu.rhn@porcupinefactory.org 2018-12-17T17:57:48Z urn:sha1:fac155815cfaa3b151a196643c90f5a1820348e3 Amended by db: simplify (subjectively) the example. lib: Explicitly state when replies will be destroyed 2019-01-26T00:34:57Z rhn gihu.rhn@porcupinefactory.org 2018-12-17T17:57:46Z urn:sha1:45639881b5ddb56492bd3ba329e982517cc9ef54 Without an explicit guarantee, it's not clear how to use the reference. lib: make notmuch_message_get_database() take a const notmuch_message_t* 2018-05-26T14:32:01Z Daniel Kahn Gillmor dkg@fifthhorseman.net 2018-05-11T06:57:54Z urn:sha1:6a9f26b4a04e20529203938a99658516876c67f3 This is technically an API change, but it is not an ABI change, and it's merely a statement that limits what the library can do. This is in parallel to notmuch_query_get_database(), which also takes a const pointer. properties: add notmuch_message_count_properties 2018-05-26T14:31:39Z Daniel Kahn Gillmor dkg@fifthhorseman.net 2018-05-11T06:57:53Z urn:sha1:499bb78178df86ceae82893fbc272c4dd1870b6c The user can already do this manually, of course, but (a) it's nice to have a convenience function, and (b) exposing this interface means that someone more clever with a _notmuch_string_map_t than i am can write a more efficient version if they like, and it will just accelerate the users of the convenience function. lib: bump minor version 2018-05-26T14:31:27Z David Bremner david@tethera.net 2018-05-23T01:47:49Z urn:sha1:4a6371f1d80aec5947b41d7c4e1fdb60cca3c55d This recognizes the addition of (at least) notmuch_message_get_database to the API. lib: expose notmuch_message_get_database() 2018-05-26T14:30:32Z Daniel Kahn Gillmor dkg@fifthhorseman.net 2018-05-11T06:57:52Z urn:sha1:9088db76d89264b733f6b45e776d8952da237921 We've had _notmuch_message_database() internally for a while, and it's useful. It turns out to be useful on the other side of the library interface as well (i'll use it later in this series for "notmuch show"), so we expose it publicly now. Merge branch 'release' 2018-04-07T20:43:01Z David Bremner david@tethera.net 2018-04-07T20:43:01Z urn:sha1:5d510221d17862a252955d98046508bebcd14573 lib: bump LIBRARY_MINOR_VERSION 2018-04-02T11:06:53Z David Bremner david@tethera.net 2018-03-27T21:30:28Z urn:sha1:920f5d925eee09d41d5c6456701854ad6d342d95 We added several new functions, at least notmuch_database_get_default_indexopts notmuch_database_index_file notmuch_indexopts_destroy notmuch_indexopts_get_decrypt_policy notmuch_indexopts_set_decrypt_policy notmuch_message_count_files notmuch_message_has_maildir_flag notmuch_message_reindex notmuch_message_remove_all_properties_with_prefix notmuch_thread_get_total_files fix typos 2018-01-05T00:35:58Z Daniel Kahn Gillmor dkg@fifthhorseman.net 2018-01-02T15:32:38Z urn:sha1:54982e520c3bee74e947e311ee5b1219396fa1a8 crypto: add --decrypt=nostash to avoid stashing session keys 2017-12-08T12:08:47Z Daniel Kahn Gillmor dkg@fifthhorseman.net 2017-12-08T06:24:02Z urn:sha1:fccebbaeef1e4b6489425afb13f419543d53d285 Here's the configuration choice for people who want a cleartext index, but don't want stashed session keys. Interestingly, this "nostash" decryption policy is actually the same policy that should be used by "notmuch show" and "notmuch reply", since they never modify the index or database when they are invoked with --decrypt. We take advantage of this parallel to tune the behavior of those programs so that we're not requesting session keys from GnuPG during "show" and "reply" that we would then otherwise just throw away.