Set up Neovim integration in VS code - visual-studio-code

Currently a (neo)vim user, I read that VS Code supports neovim backend integration, but after searching I cannot find how to set it up.
Can someone explains how to set up neovim integration in VS Code?
Thank you.
PS : I use both linux and windows so if there are some OS specifity you could mention it.

I believe the integration you read about was referring the neovim integration in VSCodeVim: https://github.com/VSCodeVim/Vim#neovim-integration

This one uses a real instance of neovim as editor back-end: https://github.com/asvetliakov/vscode-neovim

Related

NanoFramework VSCode - How to get started?

Maybe I am just missing something, but I don't get how to setup a blank solution in VSCode (Under Windows or Visual Studio, you are able to just create a new Blank NanoFramework Template, but how can I do that in VSCode :/). I would really like to work with the nanoframework instead of c/c++, but I don't know how to create a blank solution :(.
That option is not currently available.
The main goal of the VS Code extension is to allow (partially) folks on MAC or Linux to work with .NET nanoFramework.
It's not possible to debug on VS Code and you'll only have a full experience on Visual Studio. If you're on Windows, the recommendation is to use Visual Studio.

How to triger clnagd.switchSourceHeader using built-in nvim lsp

I used to do it with Coc.nvim
:CocCommand clangd.switchSourceHeader
But now I have moved to built-in nvim lsp and haven't any idea how to the same.
I found this solution for coc, but still dont how to do this for nvim lsp.
execute 'edit' CocRequest('clangd', 'textDocument/switchSourceHeader', {'uri': 'file://'.expand("%:p")})
When using the built-in LSP client, I recommend using the nvim-lspconfig plugin for configuring the servers. For clangd, it creates a command :ClangdSwitchSourceHeader (see documentation).

how to do map dependencies with code maps using VS code on ubuntu?

I encountered this link: https://learn.microsoft.com/en-us/visualstudio/modeling/map-dependencies-across-your-solutions?view=vs-2019, and I was thinking to follow it to generate code maps for my c++ code running on ubuntu vs code of version 1.61.2. Somehow I can not even find the tool menu and the solution explorer. I managed to install the solution explorer as my VS code extension. But I still do not know how to get started. Any comments are greatly appreciated.
Unfortunately it seems that the dependency maps are only available in Visual Studio and not in VSCode, which are two separate things

VSCode Intellisense Not Working In Jupyter Notebook Extension(MacOS)

I have an issue with VS Code which I recently installed in my MacOS BigSur.
I tried out the Jupyter Notebook extension and in their documentation it says that they have full intellisense support for this extension as well.
Intellisense in Jupyter Notebook in VSCode works well for completing variables, functions,methods,etc....
The only issue I have is that I am not able to get the arguments/parameter information, though it is working fine with the python extension of VSCode
I tried out things like Shift+TAB...which works in JupyterNotebooks(not the VS Code version).
Is this a bug that I am facing...or is it just like that. Can you also please suggest as to how to make this work.
Edit May 12, 2021: With the Pylance language server (now the default), I now get parameters and type hints.
According to this issue on GitHub, the arg/param info is not supported on stable VS Code. It looks like you need to use the "Native Notebook" in VS Code Insiders (the beta) and use the "Pylance" language server Extension.
I haven't tried this solution myself (not sure I want to install Insiders), but just changing the language server to "Pylance" at least gives you signatures.

Custom node version to run VSCode extensions

I'm making a vscode extension for my personal use. I'd really like to use a more recent node version. However, I'm not sure how does VSCode chooses which node version to use.
The only node.js that I have installed is 8.1.3. But when I debug the extension, I see that VSCode uses 7.*.* (via process.version).
I've been searching documentation for an hour, so far, without luck. Any help is appreciated.
This is not possible. Quoting the reply of one of the team members (Andre Weinand) in #18253:
VS Code runs extensions on the node version that is built into electron (on which VS Code is based). This cannot be changed.