-
Notifications
You must be signed in to change notification settings - Fork 82
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
Get some errors when start vim or neovim with java file. #277
Comments
Thanks |
Hello @artur-shaik! Thank you so much for developing this plugin. I use it on a regular basis when I am programming in Java. Like @wsdjeg, I too recently experience the aforementioned issue. Now after I have updated the plugin, I always see the following error message when I try to save a file:
I can confirm that I see exactly the same error message on both vim and nvim. Currently, I am running nvim and vim in tmux. I have also done several different debugging steps, like removing and reinstalling the plugin, only to receive exactly the same error message when I try to save a file. Finally, it seems as though the plugin is no longer working correctly; features that I used in the past still do not work now. I can post additional details as needed. If you have time, could you please comment on whether on not these errors are related to the fix mention in this thread? Again, thanks so much for your help! |
Hi @gkapfham , can you try to run If you get any errors, please, post it here. |
Hello @artur-shaik. Thanks again for developing this plugin. I can confirm that when I run the |
@artur-shaik it seems like lots of our issues are the result of the application needing to be compiled when the java code changes. It might be a good idea to version the server and check if the version of the server is the same as when it was last compiled. If it's not, recompile. Another plugin that does this is fzf.vim |
good idea! |
@DonnieWest good point. I thought about it some time ago, and effectively forgot to implement it. |
error message:
The text was updated successfully, but these errors were encountered: