unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Bremner <david@tethera.net>
To: Ralph Seichter <abbot@monksofcool.net>, notmuch@notmuchmail.org
Subject: Re: Notmuch, Emacs and pinentry -- oh my
Date: Fri, 08 Nov 2019 09:29:37 -0400	[thread overview]
Message-ID: <87zhh61oou.fsf@tethera.net> (raw)
In-Reply-To: <878sor9wpa.fsf@wedjat.horus-it.com>

Ralph Seichter <abbot@monksofcool.net> writes:

> Alas, in these cases I can tell that Emacs expects input of me, but it
> only uses the bottom most two lines to do so, meaning that I cannot
> quite read what is expected of me. Assuming that pinentry is involved, I
> tried switching between pinentry-curses and pinentry-tty in my shell
> profile, but the result is unreadable in both cases. If I use commands
> like "pgp -d ..." in the shell, both pinentry variants work fine (in the
> case of curse, the prompt is smack in the middle of my terminal window,
> as expected).

My only (not always popular advice) w.r.t. pinentry is to use a
graphical pinentry if at all possible.

> I have enabled 'allow-emacs-pinentry' in my gpg.conf, but that does not
> resolve the issue either, so I would be grateful for advice. Thanks.
>

Not all Emacs binaries have support for emacs-pinentry built in. Reading
gpg passphrases (or root passwords) into the same emacs as runs a mail
or irc client makes me nervous personally, but it's up to you. In any
case, if you do want to do that, check the variable
system-configuration-options.

  reply	other threads:[~2019-11-08 13:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-07 21:57 Notmuch, Emacs and pinentry -- oh my Ralph Seichter
2019-11-08 13:29 ` David Bremner [this message]
2019-11-08 13:31   ` David Bremner
2019-11-08 15:40   ` Ralph Seichter
2019-11-11 17:02     ` Daniel Kahn Gillmor
2019-11-11 19:10       ` Ralph Seichter
2019-11-12  5:59         ` Daniel Kahn Gillmor
2019-11-13 17:07           ` Ralph Seichter

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=87zhh61oou.fsf@tethera.net \
    --to=david@tethera.net \
    --cc=abbot@monksofcool.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).