You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, VSCode-R launches the R LSP by itself internally.
While for simple use-cases it sounds fine, a more advance user would like to control the exact command that is being launched for creating the LSP.
For example, in our company, we launch our R sessions only on remote machines, trough SSH. Since the language server run an R session, we'd like to run the R LSP on a remote machine.
This is done simply by running the LSP launch command in SSH(in this case the connection with VSCode is by STDIO), assuming we could have a custom command modification for LSP.
Another example is when the user would like to tweak privately the language server somehow(or hypothetically run a total different language server), and needs to tweak how this VSCode extension starts the LSP.
The text was updated successfully, but these errors were encountered:
Currently, VSCode-R launches the R LSP by itself internally.
While for simple use-cases it sounds fine, a more advance user would like to control the exact command that is being launched for creating the LSP.
For example, in our company, we launch our R sessions only on remote machines, trough SSH. Since the language server run an R session, we'd like to run the R LSP on a remote machine.
This is done simply by running the LSP launch command in SSH(in this case the connection with VSCode is by STDIO), assuming we could have a custom command modification for LSP.
Another example is when the user would like to tweak privately the language server somehow(or hypothetically run a total different language server), and needs to tweak how this VSCode extension starts the LSP.
The text was updated successfully, but these errors were encountered: