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
when my encryption subkey expires I get a message like this from gnupg.vim:
The recipient "0xXXXXXXXXXXXXXXXX" is not in your public keyring!
Would it be possible to detect that the actual cause of the failure is an expired key and report that more clearly? The current message sounds a little off for this case.
Thanks,
Antonio
The text was updated successfully, but these errors were encountered:
Would it be possible for vim-gnupg to propagate such messages to the user?
Right now, not easily. I've been contemplating changing the code to use the (neo)vim's job APIs, which would make it easier to distinguish stderr/stdout and do better error reporting.
However, I would probably want to get the change to use loopback pinentry done first. pinentry-curses (and probably pinentry-tty) really aren't meant to be used in combination with something like Vim, since they fight over the terminal. This would also resolve #32.
Hi,
when my encryption subkey expires I get a message like this from
gnupg.vim
:Would it be possible to detect that the actual cause of the failure is an expired key and report that more clearly? The current message sounds a little off for this case.
Thanks,
Antonio
The text was updated successfully, but these errors were encountered: