Closed trevarj closed 7 months ago
I'm happy to help out with fixing this but I don't have enough time to really dissect the code. I noticed there are a few issues about this in the past, so if there is any information on where this should be fixed, then I can hack around on it on my config and see if can get it to work. Thanks
Update after tinkering with the code:
client.lua:
local result = cmd.env(M.get_envs_git_editor()):in_pty(true).call_interactive { verbose = true }
making this call_interactive seems to resolve the issue perfectly.
I will put up a PR and think about how to do this only for commits and not all calls that use wrap()
I appreciate you digging into this :) The change makes sense, I think. Truth be told, call_interactive
is from before I took over this project, and I'm not entirely clear on it's semantics, save for that it's usually used for stuff like this. Lets take a look at that PR and see
@CKolkey thanks for the quick response. PR is up!
Description
With gpgSign set in gitconfig and pinentry-loopback or pinentry-tty enabled, commits cannot be made using neogit.
Relates to : https://github.com/NeogitOrg/neogit/issues/370
Neovim version
NVIM v0.10.0-dev-2489+gb413f5d04 Build type: RelWithDebInfo LuaJIT 2.1.1707061634
Operating system and version
Linux 6.7.9
Steps to reproduce
cc
Expected behavior
The user is prompted to unlock the gpg key and the changes are committed and the commit is signed.
Actual behavior
When pinentry loopback is enabled, there is just an error. When pinentry-tty is enabled without loopback, the UI gets messed up and nvim freezes
Minimal config