thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.35 2021-10-23T12:48:39Z 2021-10-23T12:48:39Z David Bremner david@tethera.net 2021-06-12T13:26:16Z urn:sha1:c128c995bc3e7474d4086af7e2066f60f54329b2 There is no reason for anything outside the indexopts.c compilation unit to have access to structure members. 2021-03-13T12:45:34Z uncrustify david@tethera.net 2021-03-13T12:45:34Z urn:sha1:8aeba1228ace947c1b689ae6ae08db5d53755917 This is the result of running $ uncrustify --replace --config ../devel/uncrustify.cfg *.c *.h *.cc in the lib directory 2020-08-03T23:45:58Z David Bremner david@tethera.net 2020-08-01T12:25:50Z urn:sha1:31dab9b1cd66c7f285fe86021f66940f679325d4 This is a rare and probably serious programming error, so better not to silently return a default value. 2019-06-14T10:41:27Z uncrustify david@tethera.net 2019-06-13T10:55:35Z urn:sha1:2b62ca2e3b786beca8d89fa737bda0b49faa638d This is the result of running $ uncrustify --replace --config ../devel/uncrustify.cfg *.c *.h *.cc in the lib directory 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. 2017-12-08T12:08:46Z Daniel Kahn Gillmor dkg@fifthhorseman.net 2017-12-08T06:23:59Z urn:sha1:076f86025d519522cde5787def6c03fc308e8ebc The new "auto" decryption policy is not only good for "notmuch show" and "notmuch reindex". It's also useful for indexing messages -- there's no good reason to not try to go ahead and index the cleartext of a message that we have a stashed session key for. This change updates the defaults and tunes the test suite to make sure that they have taken effect. 2017-12-08T12:07:53Z Daniel Kahn Gillmor dkg@fifthhorseman.net 2017-12-08T06:23:53Z urn:sha1:e4890b5bf9e2260b36bcc36ddb77d8e97e2abe7d This new automatic decryption policy should make it possible to decrypt messages that we have stashed session keys for, without incurring a call to the user's asymmetric keys. 2017-12-08T12:07:02Z Daniel Kahn Gillmor dkg@fifthhorseman.net 2017-12-08T06:23:52Z urn:sha1:798aa789b5d117cf11697bc97dd982bd5a2c2ac8 Future patches in this series will introduce new policies; this merely readies the way for them. We also convert --try-decrypt to a keyword argument instead of a boolean. 2017-12-08T12:06:03Z Daniel Kahn Gillmor dkg@fifthhorseman.net 2017-12-08T06:23:51Z urn:sha1:b62045a18680720b407173140d79b459e45e6039 This terminology makes it clearer what's going on at the API layer, and paves the way for future changesets that offer more nuanced decryption policy. 2017-12-08T12:05:53Z Daniel Kahn Gillmor dkg@fifthhorseman.net 2017-12-08T06:23:50Z urn:sha1:d3964e81ac98825a025a6120c488ebd73de2a281 the command-line interface for indexing (reindex, new, insert) used --try-decrypt; and the configuration records used index.try_decrypt. But by comparison with "show" and "reply", there doesn't seem to be any reason for the "try" prefix. This changeset adjusts the command-line interface and the configuration interface. For the moment, i've left indexopts_{set,get}_try_decrypt alone. The subsequent changeset will address those.