-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Doesn't seem to work #31
Comments
I can't reproduce this. I updated my gpg to the same version you're using (which I actually expected to cause some issues) and everything is working fine. Is gpg an alias in your shell? Are you using the latest plugin from Git or a different version? |
Yeah, I also suspected the new gpg. Here is the answer to your questions:
|
I found the issue. If I have file-line enabled, I get this behavior. Without that, it all works fine. I should've known, this plugin seems to do some buffer re-loading in a way that can beak other plugins (it breaks Fugitive in certain ways too). Sorry for the noise. |
Yeah, file-line seems to break a lot of plugins: bogado/file-line#38 (tar.vim), bogado/file-line#39 (vim-gnupg), bogado/file-line#42 (NERDTree), bogado/file-line#44 (fugitive), bogado/file-line#47 (MRU), and bogado/file-line#48 (NetRW). bogado/file-line#37 is supposed to fix it, but there's apparently a Vim issue too. |
I hate to reopen this, but I cannot seem to get this to work. I do not have any other Vim plugins installed. I've tried completely removing my ~/.vimrc as well as the system /etc/vim/vimrc configs, and still no dice. Not sure what I'm missing. Here's my environment:
The results:
|
@atoponce Your issue is completely different than the one originally reported here. You don't seem to have the plugin loaded. If you've verified, with |
I got it working after analyzing "vim -V", and verifying that it was looking for "/home/aaron/.vim/plugin/*/.vim", where I had "/home/aaron/.vim/plugins/gnupg.vim", which didn't match. Sorry for the false alarm. |
Steps:
Contents in buffer (unreadable gibberish).
Debug log:
The file is valid, and the command works:
What am I doing wrong?
The text was updated successfully, but these errors were encountered: