[PATCH] Add inside-Emacs mode to GUI pinentry programs

Daiki Ueno ueno at gnu.org
Sun Jun 14 03:24:04 CEST 2015


Daiki Ueno <ueno at gnu.org> writes:

> Perhaps we could integrate it into pinentry_loop?
>
>> Also, why don't you modify the curses and tty frontends to support
>> emacs?
>
> I just forgot that, since the implementation started based on the curses
> fallback.  I will send a new patch soon.

Here is a new patch, modified along these lines.  Changes from the
previous version are:

- pinentry_enable_emacs_cmd_handler is now called from option_handler,
  and all hooks in gnome3/gtk+-2/qt4 are removed
- the allow-emacs-prompt Assuan option patch is squashed into this
- the UID value check is now replaced with simple cast to uint32_t,
  using configure time check

"Neal H. Walfield" <neal at walfield.org> writes:

> Thus, if allow-emacs-pinentry is not set (1) and we don't forward the
> INSIDE_EMACS environment variable (2), then pinentry won't try the
> emacs pinentry (3).
>
> Therefore, teaching pinentry about this option is not required.
>
> Does that make sense or do you have another use case in mind that I'm
> missing?

As Werner already pointed, (2) is not always the case with the current
code.

However, perhaps the above scenario might be actually possible by
explicitly unsetenv'ing INSIDE_EMACS in gpg-agent, when
allow-emacs-pinentry is not set in gpg-agent.conf (like we do for
DISPLAY, when keep-display is not set).

Regards,
-- 
Daiki Ueno
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Add-inside-Emacs-mode-to-GUI-pinentry-programs.patch
Type: text/x-diff
Size: 28347 bytes
Desc: not available
URL: </pipermail/attachments/20150614/4994af8a/attachment-0001.patch>


More information about the Gnupg-devel mailing list