Replies: 4 comments 2 replies
-
Gosh! That's a hell of configuration and documentation! So, in my original Packer plugins file (not updated yet to Lazy) I have to set this: if vim.g.vscode then
-- VSCode extension
else
-- ordinary Neovim
end ...and all my Nvim plugins I want to use in VS Code I list in Then, in the documentation is always mentioned the So, if I want to use keymaps like in Neovim, I have to put them in my Neovim keymaps file (mixing Nvim configuration with VSC-Nvim configuration?!) or I create a new one only for using in VSC (then I have two places that I have to care of?!)? Can show me somebody a well written Lua configuration for this extension? |
Beta Was this translation helpful? Give feedback.
-
Yes. Or rather, the parts you want to include/exclude conditionally for vscode, go in that if/else block. The rest of your nvim config will "mostly" work. If you find some plugin that doesn't work well, then its configuration should go in the There are numerous examples in the readme showing how to call vscode commands (the same id that you would call in vscode itself): https://github.com/vscode-neovim/vscode-neovim?tab=readme-ov-file#examples |
Beta Was this translation helpful? Give feedback.
-
My leader key is regularly defined at the very top of this So... why this doesn't work as key mapping? The if/else for plugins I do not have tested right now. Any recommendations? |
Beta Was this translation helpful? Give feedback.
-
By now, I have translated the vim script stuff from the documentation to Lua (there are plenty of examples :'D ...but I didn't see them in Lua like in my examples above). I've installed now the regular Vim extension in VS Code and deleted the Neovim extension. The Vim extension is way better. Way better written documentation, setting it up is super straight forward and easy. I've achieved with the Vim extension in two hours what I've not achieved with the Neovim extension in 2.5 days. So, if I like to play around and enjoy wasting a lot of time, I choose the Neovim extension. If I have to get work done fast and seriously I use the Vim extension. Regularly I will stay with my Neovim setup in terminal. VS Code is only for collaborations with Live Share, but I need my Neovim/Vim controls to be fast. So in my case, there is no time to have a childish play around with this Neovim extension. |
Beta Was this translation helpful? Give feedback.
-
Like in the documentation explained, I've created a
keybindings.json
.This is the very whole content of it:
I want to use
<Leader>/
to comment in/out a line, but it doesn't work. Is there something wrong with my keybinding? Did I've misunderstood something?Beta Was this translation helpful? Give feedback.
All reactions