[pkg-gnupg-maint] Bug#509554: pinentry-curses destroys terminal settings

[Antonio Ospite]

Package: pinentry-curses
Version: 0.9.7-9
Followup-For: Bug #509554

Dear Maintainer,

I still experience this issue with the vim-gnupg[1] plugin after
I disable a workaround[2,3] its author added. JFYI I disable the
workaround because it has side effects[4].

So I looks like no proper solution was found in pinentry-curses (or
vim?).

This is how to reproduce the issue with vim 8.0, assuming you are not
using the vim-gnupg plugin already.

1. Download the vim-gpg plugin and disable the workaround:

  $ mkdir -p ~/.vim/pack/pinentry-curses_test/start/
  $ cd  ~/.vim/pack/pinentry-curses_test/start/
  $ git clone https://github.com/jamessan/vim-gnupg.git
  $ sed -e 's/[^"]\(let &term = &term\)/"\1/' -i vim-gnupg/plugin/gnupg.vim

2. Create an encrypted file and open it with the vim-gnupg plugin and
   pinentry-ncurses:

  $ sudo update-alternatives --set pinentry /usr/bin/pinentry-curses
  $ echo RELOADAGENT | gpg-connect-agent
  $ (echo LINE1 ; echo LINE2) | gpg -e > encrypted.gpg
  $ vim encrypted.gpg

The arrow keys in vim do not work anymore.

Thanks,
   Antonio

[1] https://github.com/jamessan/vim-gnupg
[2] https://github.com/jamessan/vim-gnupg/commit/bd3ebdff6cb18d09c4bdbb72e28e07841c5076eb
[3] https://github.com/jamessan/vim-gnupg/issues/17
[4] https://github.com/jamessan/vim-gnupg/issues/64

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (900, 'unstable'), (500, 'unstable-debug')
Architecture: amd64 (x86_64)

Kernel: Linux 4.8.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages pinentry-curses depends on:
ii  libassuan0     2.4.3-1
ii  libc6          2.24-5
ii  libgpg-error0  1.24-2
ii  libncursesw5   6.0+20160917-1
ii  libtinfo5      6.0+20160917-1

pinentry-curses recommends no packages.

Versions of packages pinentry-curses suggests:
pn  pinentry-doc  <none>

-- no debconf information
-- 
Antonio Ospite
https://ao2.it
https://twitter.com/ao2it

A: Because it messes up the order in which people normally read text.
   See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?