unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Daniel Patterson <dbp@dbpmail.net>
Cc: notmuch@notmuchmail.org
Subject: Re: Emacs not finding keys to verify signatures
Date: Sun, 30 Jun 2013 16:05:34 -0400	[thread overview]
Message-ID: <51D08F8E.4010805@fifthhorseman.net> (raw)
In-Reply-To: <878v1tdjo0.fsf@thinkpad.i-did-not-set--mail-host-address--so-tickle-me>

[-- Attachment #1: Type: text/plain, Size: 763 bytes --]

On 06/29/2013 11:24 AM, Daniel Patterson wrote:

> This works. Thanks a lot!

great!

> Yeah, it would be good if there were a hook to be able to send to remote
> gpg... because everything else works so smoothly with simple
> wrappers. Even if it were just a matter of setting a custom gpg command
> (like gpg-notmuch, which would be a shell script that would send the
> calls to the remote gpg).

i think the command would be "notmuch gpg", not "gpg-notmuch" -- in your
configuration, how does emacs know to invoke notmuch on the remote
server instead of locally?  is it possible that we could make this
change something that happens in exactly one place in the emacs
configuration, and have the wrapper scripts figure out the rest?

	--dkg


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 1027 bytes --]

  reply	other threads:[~2013-06-30 20:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-24 14:59 Emacs not finding keys to verify signatures Daniel Patterson
2013-06-28 11:18 ` David Bremner
2013-06-28 13:11   ` Daniel Patterson
2013-06-28 15:05     ` David Bremner
2013-06-28 15:13       ` Daniel Kahn Gillmor
2013-06-29 15:24         ` Daniel Patterson
2013-06-30 20:05           ` Daniel Kahn Gillmor [this message]
2013-06-30 20:13             ` Daniel Patterson

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=51D08F8E.4010805@fifthhorseman.net \
    --to=dkg@fifthhorseman.net \
    --cc=dbp@dbpmail.net \
    --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).