unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Tomi Ollila <tomi.ollila@iki.fi>
To: David Bremner <david@tethera.net>, notmuch@notmuchmail.org
Subject: Re: emacs: use epg-gpg-program
Date: Mon, 13 Mar 2017 22:17:09 +0200	[thread overview]
Message-ID: <m237eh2apm.fsf@guru.guru-group.fi> (raw)
In-Reply-To: <87a88qp25u.fsf@tethera.net>

On Mon, Mar 13 2017, David Bremner <david@tethera.net> wrote:

> Tomi Ollila <tomi.ollila@iki.fi> writes:
>
>> From: John Byrnes <john@johnbyrnes.info>
>>
>> From: John Byrnes <john@johnbyrnes.info>
>>
>> Adjusted notmuch-crypto gpg call-process function to respect
>> the GPG program set by the EasyPG epg-gpg-program variable.
>>
>> This is to correct a problem observed on NixOS where only gpg2 is
>> installed by default. The Notmuch Emacs frontend fails when trying to
>> access someone's key to verify their signature when it cannot find the
>> GPG binary.
>
> Following Tomi's hint on IRC I ran
>
> emacs -Q --batch --eval "(progn (package-initialize) (require 'notmuch) (message epg-gpg-program))"
>
> and it seems epg-gpg-program is defined. On the other hand can anyone
> think of a good reason not to add (require 'epg) to the top of
> notmuch-crypto.el?

IMO amending one From: line out and adding that is a good idea,
to explicitly require a module which feature is being used.

Currently it looks like egp is loaded by mml-sec, which is loaded by
mml-smime which is loaded by mm-view which is loaded by notmuch.el as the
first module it is requiring (used try-emacs-mua to see what it is loading
and then manually parsed the output)


Tomi

>
> d

  reply	other threads:[~2017-03-13 20:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-12 19:26 emacs: use epg-gpg-program Tomi Ollila
2017-03-12 22:21 ` David Bremner
2017-03-13 20:17   ` Tomi Ollila [this message]
2017-03-14  0:19     ` 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=m237eh2apm.fsf@guru.guru-group.fi \
    --to=tomi.ollila@iki.fi \
    --cc=david@tethera.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).