You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I updated from gnupg.vim 2.5 to 2.6 and I started to notice that xterm flickers when opening a .gpg file with vim, before showing the key prompt from gpg. The issue is a lot more visible with a full screen xterm.
I do not see the issue with other terminal emulators, so it might be a xterm+vim issue which gnupg.vim triggers; I bisected the history and I found out that the issue has been introduced in commit bd3ebdf from issue #17.
For now I can live with just commenting the term rediscovery workaround, but I wanted tor report that the workaround from commit bd3ebdf may have side effects like the one I am experiencing.
Thanks,
Antonio
The text was updated successfully, but these errors were encountered:
@jamessan if there is no easy solution could we make the workaround optional, guarding it with a config variable?
Even with a default to ON it'd be OK for me, so I can at least disable it via .vimrc instead of patching the plugin.
I can send a patch for that if the approach is fine with you.
Just for the records, by reverting the workaround from bd3ebdf and using pinentry-tty I avoid both the issue from #17 and the flickering from this issue.
Hi,
I updated from
gnupg.vim
2.5 to 2.6 and I started to notice that xterm flickers when opening a .gpg file with vim, before showing the key prompt from gpg. The issue is a lot more visible with a full screen xterm.I do not see the issue with other terminal emulators, so it might be a xterm+vim issue which
gnupg.vim
triggers; I bisected the history and I found out that the issue has been introduced in commit bd3ebdf from issue #17.For now I can live with just commenting the term rediscovery workaround, but I wanted tor report that the workaround from commit bd3ebdf may have side effects like the one I am experiencing.
Thanks,
Antonio
The text was updated successfully, but these errors were encountered: