Hi Antonio-- On Mon 2016-11-14 23:45:55 +0900, Antonio Ospite wrote: > 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].
I don't think #509554 was about the gpg plugin -- was it? (i'm not a vim user). It sounds like you might be asking about a different issue -- maybe it should be a new bug report? > 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 Arbitrary plugins for vim can produce arbitrary errors -- Does this problem happen with the gnupg.vim in the vim-scripts package in debian? --dkg
signature.asc
Description: PGP signature
