Issue when neogit is prompting pinentry-mac
on macOS.
#269
molleweide
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi Tim,
I don't know if this really is a bug pertaining to neogit so I create it under discussion here. My problem is as follows:
If I am correct there is an issue with using neogit and gpg pinentry. Personally I am using
pinentry-mac
as pervim-gnupg
issue thread jamessan/vim-gnupg#32 and it seems I can open an encrypted file with no problems using
the vim built in
:edit mydecryptedfile.gpg
but committing withneogit
and gpg enabled creates problems.The issue that occurs with
neogit
, if I am correct, which I might very well not be (maybe this pertains to something else), is something similar to what jamessan/vim-gnupg#32 (comment) is describing.This is a quote taken from the comment referenced above:
Important note that I forgot to add first, is that if I use successfully log in to my keychain outside of neovim, or outside of neogit, then neogit will sign commits without a problem. This issue only pertains to when neogit is prompting
pinentry-mac
.consistency
I have tried disabling and re-enabling gpg a couple of times and neogit consistently fails with gpg pinentry on my mac.
Please tell me if there is anything you would like to, or recommend me, to test in order to debug the issue.
provided screenshots
success; decrypting with
:e
This is a screenshot of successfully opening a decrypted file with
pinentry-mac
:This is what it looks like when neogit prompts pinentry:
System and Doom Nvim information
doom_root
variable:/Users/hjalmarjakobsson/.config/doom-nvim
doom_configs_root
variable:/Users/hjalmarjakobsson/.config/doom-nvim
do you have a sponsor /donations page?
todo
I shall learn how to commit with some other git plugins and try to narrow it down if this issue pertains to neogit.
Beta Was this translation helpful? Give feedback.
All reactions