vscode-neovim: bug: Extension doesn't work correctly after updating to 1.14.*
Check the following:
- I have checked the behavior after setting “vscode-neovim.neovimClean” in VSCode settings.
- I have read the vscode-neovim docs.
- I have searched existing issues.
Neovim version (nvim -v)
NVIM v0.9.5
Operating system/version
Windows 11
Describe the bug
After updating the extension to the latest version I get the following output from “vscode-neovim messages”
Error detected while processing VimEnter Autocommands for "*":
E116: Invalid arguments for function nvim_exec2
Also, when scrolling in any code, everything gets fumbled.
Steps To Reproduce
- Update to version 1.14.* (tested with both 1.14.0 and 1.14.1) of the extension
- It’s messed up
Expected Behavior
That the extension works after updating.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 3
- Comments: 24
Commits related to this issue
- Move vscode folder to config https://github.com/vscode-neovim/vscode-neovim/issues/2040 — committed to Emin017/nvim by Emin017 2 years ago
- Worked around https://github.com/vscode-neovim/vscode-neovim/issues/2040 — committed to vdchs/nvim-config by deleted user 2 years ago
I guess you have
lua/vscodeorlua/vscode.luain your config directory.Renaming the file
lua/vscode.luato other name can solve the problem.Version 1.14.2 will tell you where the issue lies.
It is, I was wrong. Simply put in your case you had made the namespace conflict by naming the files explicitly that resulted in collision, in my case a plugin I had installed created a namespace conflict.
For personal configurations, it is recommended to place them in an individual module, such as lua/self, lua/username, etc.