PGP/MIME signature verification
On Sat, 27 Nov 2010 14:35:03 -0500, Daniel Kahn Gillmor wrote: > the signature-verification branch on my git repo [0] contains functional > PGP/MIME signature verification if you supply the --verify argument to > > notmuch show --format=json > > It relies on gpg being in the path, and on the user having the signer's > key in their gnupg keyring. I was able to merge dkg's signature-verification branch on top of cworth's current master head (b3caef1f) with only a tiny easily-resolvable conflict. It seems to work exactly as advertised, and I wholeheartedly approve and endorse this patch set for inclusion upstream: Approved-and-Tested-By: Jameson Rollins I have pushed a merged "signature-verification" branch to my repo, along with a single commit to fix an errant newline in the json --verify output: git://finestructure.net/notmuch Carl: can you give an indication of whether or not you intend to ultimately accept this patch set? If so, I would like to start work on representing signature verification information in the emacs UI. I want to make sure that we're good with this effort first, though. We should probably also start a conversation about how best to represent the signature verification info. I'll bring that up in a separate thread, though. dkg: again, great work on this! Thanks! Next up: decrypting! jamie. -- next part -- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 835 bytes Desc: not available URL: <http://notmuchmail.org/pipermail/notmuch/attachments/20101220/749f9af2/attachment.pgp>
Re: PGP/MIME signature verification
On Sat, 27 Nov 2010 14:35:03 -0500, Daniel Kahn Gillmor wrote: > the signature-verification branch on my git repo [0] contains functional > PGP/MIME signature verification if you supply the --verify argument to > > notmuch show --format=json > > It relies on gpg being in the path, and on the user having the signer's > key in their gnupg keyring. I was able to merge dkg's signature-verification branch on top of cworth's current master head (b3caef1f) with only a tiny easily-resolvable conflict. It seems to work exactly as advertised, and I wholeheartedly approve and endorse this patch set for inclusion upstream: Approved-and-Tested-By: Jameson Rollins I have pushed a merged "signature-verification" branch to my repo, along with a single commit to fix an errant newline in the json --verify output: git://finestructure.net/notmuch Carl: can you give an indication of whether or not you intend to ultimately accept this patch set? If so, I would like to start work on representing signature verification information in the emacs UI. I want to make sure that we're good with this effort first, though. We should probably also start a conversation about how best to represent the signature verification info. I'll bring that up in a separate thread, though. dkg: again, great work on this! Thanks! Next up: decrypting! jamie. pgpb9fBx8uRpm.pgp Description: PGP signature ___ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch
Bug in emacs showing long threads
On Sun, 19 Dec 2010 22:27:05 -0500, Scott Henson wrote: > I've been having problems with really long threads for a while when > using notmuch. When I click on them in emacs to display the content, > I get "Lisp nesting exceeds `max-lisp-eval-depth'" Hi Scott, have you tried just bumping up the value of max-lisp-eval-depth from its default value? I'm not sure that gets at the root of the problem but it should at least make the threads viewable. Try adding to your .emacs, something like: (setq max-lisp-eval-depth 1000) -- next part -- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: <http://notmuchmail.org/pipermail/notmuch/attachments/20101220/a3093801/attachment.pgp>
Re: Bug in emacs showing long threads
On Sun, 19 Dec 2010 22:27:05 -0500, Scott Henson wrote: > I've been having problems with really long threads for a while when > using notmuch. When I click on them in emacs to display the content, > I get "Lisp nesting exceeds `max-lisp-eval-depth'" Hi Scott, have you tried just bumping up the value of max-lisp-eval-depth from its default value? I'm not sure that gets at the root of the problem but it should at least make the threads viewable. Try adding to your .emacs, something like: (setq max-lisp-eval-depth 1000) pgpAmlfC2xiAa.pgp Description: PGP signature ___ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch
