On Tue 2018-06-12 23:07:33 -0700, Jameson Graef Rollins wrote: > What if notmuch-crypto-process-mime just accepted the same values that > show --decrypt does, with the same meanings, e.g.: > > ┌─────────────────────────────────────┬───────┬──────┬──────┬───────┐ > │ │ false │ auto │ true │ stash │ > ├─────────────────────────────────────┼───────┼──────┼──────┼───────┤ > │Show cleartext if session key is │ │ X │ X │ X │ > │already known │ │ │ │ │ > ├─────────────────────────────────────┼───────┼──────┼──────┼───────┤ > │Use secret keys to show cleartext │ │ │ X │ X │ > ├─────────────────────────────────────┼───────┼──────┼──────┼───────┤ > │Stash any newly recovered session │ │ │ │ X │ > │keys, reindexing message if found │ │ │ │ │ > └─────────────────────────────────────┴───────┴──────┴──────┴───────┘ > > notmuch-crypto-process-mime is really only relevant for show anyway, so > I think this makes sense. I agree, i think this makes sense. so these text strings could be mapped straight through. in addition to the strings, for the sake of supporting more native elisp-y style, if notmuch-crypto-process-mime is set to nil it should probably map to "false", and if it is set to t, it should probably map to "true". wdyt? --dkg _______________________________________________ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch