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. image

Steps To Reproduce

  1. Update to version 1.14.* (tested with both 1.14.0 and 1.14.1) of the extension
  2. 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

Most upvoted comments

I guess you have lua/vscode or lua/vscode.lua in your config directory.

Renaming the file lua/vscode.lua to other name can solve the problem.

Version 1.14.2 will tell you where the issue lies.

I dont believe that it was namespace conflict.

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.