VSCode Ruby-LSP failed to activate because `rbenv exec` does not exist.

[carnoxen]

Progress

1. Install rbenv-for-windows
2. Install vscode, and add ruby-lsp plugin
3. Set version manager to rbenv

Happening

Ruby-LSP tried executing rbenv exec but it failed.

[ccmywish]

According to my test, you don't need to configure the version manager in ruby-lsp.

In the latest ruby-lsp, even if you choose the version manager to rbenv, even if rbenv exec indeed failed, the next step, ruby-lsp will use pure ruby.exe. In the design of rbenv-for-Windows, ruby.exe always point to the right version, so ruby-lsp still works correctly.

Because I found that ruby-lsp only uses cmd.exe to start the command, so just make sure that your cmd.exe can execute ruby.exe in rbenv-for-Windows.