From: Jameson Graef Rollins <jrollins@finestructure.net>
To: Jani Nikula <jani@nikula.org>, David Bremner <david@tethera.net>,
notmuch@notmuchmail.org
Subject: Re: [PATCH] cli: crypto: tell gmime to use gpg-agent
Date: Thu, 28 Feb 2013 16:10:51 -0800 [thread overview]
Message-ID: <87vc9cm12s.fsf@servo.finestructure.net> (raw)
In-Reply-To: <87txoxwf1a.fsf@nikula.org>
[-- Attachment #1: Type: text/plain, Size: 664 bytes --]
On Wed, Feb 27 2013, Jani Nikula <jani@nikula.org> wrote:
> If the user wants to have decryption in notmuch, the user *must* use
> gpg-agent, regardless of this change or the "use-agent" configuration
> option. There is no opt out if one wants to have decryption in notmuch,
> regardless of this change.
I think this point makes sense. I guess my main worry was that querying
the agent would have unintended consequences for someone who is not
expecting it or specifically does not want it to be queried. But maybe
the point is that if they don't want that to happen, then they should
just not call notmuch with --decrypt. I suppose that's reasonable.
jamie.
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
next prev parent reply other threads:[~2013-03-01 0:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-27 7:40 [PATCH] cli: crypto: tell gmime to use gpg-agent Jani Nikula
2013-02-27 8:45 ` Tomi Ollila
2013-02-27 16:14 ` Jameson Graef Rollins
2013-02-27 17:11 ` David Bremner
2013-02-27 17:25 ` Jameson Graef Rollins
2013-02-27 22:46 ` Jani Nikula
2013-03-01 0:10 ` Jameson Graef Rollins [this message]
2013-03-01 6:12 ` Daniel Kahn Gillmor
2013-03-01 6:52 ` Tomi Ollila
2013-03-01 16:43 ` [PATCH] man: show and reply --decrypt option requires gpg-agent Jani Nikula
2013-03-01 16:56 ` Jameson Graef Rollins
2013-03-02 14:48 ` [PATCH] cli: crypto: tell gmime to use gpg-agent 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=87vc9cm12s.fsf@servo.finestructure.net \
--to=jrollins@finestructure.net \
--cc=david@tethera.net \
--cc=jani@nikula.org \
--cc=notmuch@notmuchmail.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).