thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.26_rc2 2017-12-29T20:45:55Z 2017-12-29T20:45:55Z Daniel Kahn Gillmor dkg@fifthhorseman.net 2017-12-19T16:40:55Z urn:sha1:af8255fb7159652a7d4e1fe4f1398302e1746cce This brings the --decrypt argument to "notmuch reply" into line with the other --decrypt arguments (in "show", "new", "insert", and "reindex"). This patch is really just about bringing consistency to the user interface. We also use the recommended form in the emacs MUA when replying, and update test T350 to match. 2017-12-29T20:45:46Z Daniel Kahn Gillmor dkg@fifthhorseman.net 2017-12-19T16:40:54Z urn:sha1:8ea4a99d74737929f58568505e41c94f65a14743 We also expand tab completion for it, update the emacs bindings, and update T350, T357, and T450 to match. Make use of the bool-to-keyword backward-compatibility feature. 2017-12-15T01:28:50Z Jani Nikula jani@nikula.org 2017-11-02T18:44:59Z urn:sha1:f3fc97c0008c1d48ccac88c52b5bae61460bfa3f The notmuch address output is much more useful for scripts with just the addresses printed. Support this using the --output=address option. 2017-12-11T13:11:19Z Daniel Kahn Gillmor dkg@fifthhorseman.net 2017-10-26T21:28:12Z urn:sha1:94dc81a91b2f300d1c583cc10956869d29c645a8 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:57Z urn:sha1:181d4091c408b8ca014ec245ecdae602942b70ce we also include --decrypt=auto in the tab completion. 2017-12-08T12:08:46Z Daniel Kahn Gillmor dkg@fifthhorseman.net 2017-12-08T06:23:55Z urn:sha1:a1260896f6b2beb82f46c41663f00cb42a4c5ce7 When showing a message, if the user doesn't specify --decrypt= at all, but a stashed session key is known to notmuch, notmuch should just go ahead and try to decrypt the message with the session key (without bothering the user for access to their asymmetric secret key). The user can disable this at the command line with --decrypt=false if they really don't want to look at the e-mail that they've asked notmuch to show them. and of course, "notmuch show --decrypt" still works for accessing the user's secret keys if necessary. 2017-12-08T12:08:46Z Daniel Kahn Gillmor dkg@fifthhorseman.net 2017-12-08T06:23:54Z urn:sha1:6802b333eb356fdeafd97a4e4ed74999d055a852 If the user doesn't specify --decrypt= at all, but a stashed session key is known to notmuch, when replying to an encrypted message, notmuch should just go ahead and decrypt. The user can disable this at the command line with --decrypt=false, though it's not clear why they would ever want to do that. 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. 2017-10-21T22:58:52Z Daniel Kahn Gillmor dkg@fifthhorseman.net 2017-10-21T02:25:48Z urn:sha1:81168917447a582aee186fc0edc09f5277ce565d Enable override of the index.try_decrypt setting on a per-run basis when invoking "notmuch reindex". This allows the possibility of (for example) an emacs keybinding that adds the cleartext of the currently shown decrypted message to the index, making it searchable in the future. It also enables one-time indexing of all messages matching some query, like so: notmuch reindex tag:encrypted and\ not property:index.decryption=success and\ from:alice@example.org We also update the documentation and tab completion, and add a few more tests.