Issue committing with locked signing key

[danjones1618]

I currently have my pinentry program set to pinentry-curses for unlocking my signing key

When using fugitive to :G commit when the key is locked it will start pinentry-curses to request the signing key password.
However, when this happens it renders over vim and upon exiting vim is looks messed up as the background of pinentry-curses is still present. This can be reset by doing ! to re-render vim

Is there any way around this?

[tpope]

I would expect this not to work: The interaction model of :Git necessitates the use of a dumb terminal, which is pinentry-tty territory, not pinentry-curses. But it sounds like what is happening is that pinentry-curses is getting its hands on Vim's tty and trashing it.

What Vim version? What OS? What is :echo g:fugitive_pty (expected to be an undefined variable)?

[danjones1618]

That explanation makes perfect sense.
If it's not possible then I'll just switch to pinentry-tty

Version: VIM 8.2 (from arch repos)
OS: Arch Linux
:echo g:fugitive_pty: Undefined variable

[tpope]

Can you tell me if you have $GPG_TTY set or are doing anything else similarly nefarious?

[danjones1618]

Just export GPG_TTY=$(tty)

[tpope]

Well that would certainly explain it. You're telling GPG to hijack the current TTY away from Vim, so it's no surprise that the screen gets garbled without Vim knowing about it. I think I'll fix it by blanking out GPG_TTY when calling git.

[danjones1618]

That makes sense. Iirc the rational behind it is to do with ssh-ing into the machine
Thanks!

[tpope]

I found a workaround, but it's not pretty. Put this in /usr/local/bin/gpg or anywhere else that outranks /usr/bin in $PATH:

#!/bin/sh

if [ -n "$FUGITIVE" ]; then
  set -- --pinentry-mode loopback "$@"
fi
exec /usr/bin/gpg "$@"

Alternatively, give the script a different name, and configure gpg.program in Git to point at it.

[danjones1618]

That worked thank you so much!