-
I would love to use this extension but I can't get it to work. I must have misunderstood something. My setup: NVIM v0.9.5 / VSCode 1.86.2 / vscode-neovim v1.6.1 I started with a simple if vim.g.vscode then
print("nvim-vscode")
else
print("nvim")
end My {
// NeoVim
"extensions.experimental.affinity": {
"asvetliakov.vscode-neovim": 1
},
"vscode-neovim.logLevel": "info",
"vscode-neovim.logOutputToConsole": true
} Now, when I open a document in VSCode i see the following in the dedug log:
which for a start tells me, that the Can someone help me to get this working? Am I missing something? Are there better ways to debug this? Thanks. Any help is appreciated. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 5 replies
-
Seems like your
Maybe some vscode mappings are interfering. Try removing your vscode shortcuts (rename/backup your |
Beta Was this translation helpful? Give feedback.
-
Thanks for the followup. If you can find a way that vscode-neovim could detect this situation (i.e. some Nvim state or logs that can be checked), please create an issue. We have created similar checks, for example: #1816 |
Beta Was this translation helpful? Give feedback.
Alright, I can't find the exact problem with my setup at the moment. So I decided to go with the AppImage NeoVim version.
I modified my
settings.json
in VSCode as follows:This works for me. So, when in VSCode it uses the AppImage and when i use NeoVim directly I use my with
brew
installed version.Thanks again @justinmk for giving me some hints!!