Is your feature request related to a problem? Please describe.
Nvim remote currently expects users to allow X-forwarding to the neovim remote instance, and can be a problem for RDP/VNC. Having a more traidtional VSCode tunnels is useful when developing in devcontainers. Microsoft tunnels is an MS feature - and cannot be supported. I came across [https://github.com/mikew/nvrh|nvrh]. This works with first party support in neovim and forwards ports.
Describe the solution you'd like
Forwarding ports using nvrh, so we can get a VS Code remote development experience with remote-nvim so it is truly remote nvim.
Describe alternatives you've considered
X-Forwarding neovim like described by this project. Port forwarding, clipboard, neovim inside docker - these are not always easily supported, and breaks extensions supported in the host operating system.
Is your feature request related to a problem? Please describe.
Nvim remote currently expects users to allow X-forwarding to the neovim remote instance, and can be a problem for RDP/VNC. Having a more traidtional VSCode tunnels is useful when developing in devcontainers. Microsoft tunnels is an MS feature - and cannot be supported. I came across [https://github.com/mikew/nvrh|nvrh]. This works with first party support in neovim and forwards ports.
Describe the solution you'd like
Forwarding ports using nvrh, so we can get a VS Code remote development experience with remote-nvim so it is truly remote nvim.
Describe alternatives you've considered
X-Forwarding neovim like described by this project. Port forwarding, clipboard, neovim inside docker - these are not always easily supported, and breaks extensions supported in the host operating system.