Daniel Kahn Gillmor writes:
> I worry that this is due to one of the two following commits but my
> elisp-foo is weak enough that i don't know what the right next steps are:
It's due to the second commit, 05a436f7 (emacs: don't fset keymaps,
2020-11-11). You could avoid the error by dropping the
I just tried to upgrade notmuch to the head of development. my ~/.emacs
contains a stanza for a shortcut for dealing with junk mail, which has
given me no problems at all for notmuch 0.31.4-1:
-
;; notmuch junk handling
(defun dkg-notmuch-show-handle-junk ()
"Mark the message as spam, a
Most concrete verification steps are likely only taken on the e-mail
address in the first place, and e-mail addresses render more
intelligibly than arbitrary User IDs in the first place.
Signed-off-by: Daniel Kahn Gillmor
---
emacs/notmuch-crypto.el | 15 ++-
1 file changed, 10 inser
When the certificate that signs a message is known to be valid, GMime
is capable of reporting on the e-mail address embedded in the
certificate.
We pass this information along to the caller of "notmuch show", as
often only the e-mail address of the certificate has actually been
checked/verified.
Hi folks--
id:e4a7efe92433f7c3e5dedeac0ea4efc003020296.ca...@ericsson.com from the
IETF LAMPS WG mailing list can be found at
https://mailarchive.ietf.org/arch/msg/quic/FpbJTLXsoFLSNr--LgxCOC6IssY.
when rendering it, notmuch-emacs shows:
[ Good signature by:
1.2.840.113549.1.9.1=#6D61676E
