From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Jameson Graef Rollins <jrollins@finestructure.net>,
David Bremner <david@tethera.net>,
Vagrant Cascadian <vagrant@debian.org>,
755544@bugs.debian.org
Cc: notmuch@notmuchmail.org
Subject: Re: Bug#755544: notmuch-emacs: doesn't check gpg/pgp signatures by default
Date: Tue, 22 Jul 2014 00:30:48 -0400 [thread overview]
Message-ID: <53CDE8F8.8050200@fifthhorseman.net> (raw)
In-Reply-To: <87iomqxkzp.fsf@servo.finestructure.net>
[-- Attachment #1: Type: text/plain, Size: 748 bytes --]
On 07/21/2014 09:03 PM, Jameson Graef Rollins wrote:
> On Mon, Jul 21 2014, David Bremner <david@tethera.net> wrote:
>> notmuch folks: it seems that in vagrant's message, and several others I
>> checked, it notmuch-crypto-process-mime==nil, then no signature button
>> is created at all.
>
> Yes, this is true. The signature button is pretty meaningless if we're
> not processing the signature.
>
> Maybe instead by default we could have a signature button that opens up
> a notmuch-crypto-process-mime customization buffer?
Or the button could just re-load the current view while processing the
signature, and send "you can customize notmuch-crypt-process-mime to do
this automatically in the future" to *Messages*.
--dkg
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 949 bytes --]
next prev parent reply other threads:[~2014-07-22 4:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140721223426.GA5250@siren>
2014-07-21 23:16 ` Bug#755544: notmuch-emacs: doesn't check gpg/pgp signatures by default David Bremner
2014-07-22 1:03 ` Jameson Graef Rollins
2014-07-22 4:30 ` Daniel Kahn Gillmor [this message]
2014-07-22 4:39 ` Daniel Kahn Gillmor
2014-07-22 9:44 ` David Bremner
2016-02-08 17:46 ` David Edmondson
2017-07-16 12:45 ` David Bremner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53CDE8F8.8050200@fifthhorseman.net \
--to=dkg@fifthhorseman.net \
--cc=755544@bugs.debian.org \
--cc=david@tethera.net \
--cc=jrollins@finestructure.net \
--cc=notmuch@notmuchmail.org \
--cc=vagrant@debian.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).