jamessan / vim-gnupg

This script implements transparent editing of gpg encrypted files.
http://www.vim.org/scripts/script.php?script_id=3645
729 stars 73 forks source link

Conflict with file-line plugin #93

Closed Xophmeister closed 6 years ago

Xophmeister commented 6 years ago

I believe this is probably a problem I have with a conflicting plugin, rather than a bug with vim-gnupg. However, whenever I open an encrypted file, the decrypted contents flash up in the buffer (after pinentry does its thing), but then are immediately replaced with (presumably) the original encrypted contents. In the status bar, the filename is shown, appended with [noeol][converted].

I'm using Vim 8.1 with vim-gnupg 2.6.1; actually, master as of 22cbc6b, but it's been like this for a while (it's just never been an issue for me, personally, before now). I have the following plugins (all at their master HEAD, as of just now):

jamessan commented 6 years ago

My suggestion is to bisect your plugins and find out which one is causing the problem. Then we can discuss if there's anything I can do for vim-gnupg.

Xophmeister commented 6 years ago

It looks like it's file-line that's causing the problem. If I disable this plugin, everything works as I expect. To be honest, I never use this plugin, so I'll just get rid of it and close this issue, after renaming it in case others have a similar problem.

jamessan commented 6 years ago

Ah, yeah, this has come up before -- https://github.com/jamessan/vim-gnupg/issues/25 and https://github.com/jamessan/vim-gnupg/issues/31#issuecomment-92159243.

Maybe https://github.com/wsdjeg/vim-fetch works better.