Open
Description
This issue explores the open questions on r-devel/r-dev-env#193 (comment).
We have established the following procedure for connecting a local Positron IDE to the R Dev Container running on Gitpod:
- Start the Dev Container as a Gitpod workspace.
- From https://gitpod.io/workspaces, click on the three dots next to the workspace to expand the menu, select Connect via SSH. If necessary set up an SSH key. Copy the command, something like (modified from actual!):
and paste it somewhere for reference.
ssh 'rdevel-rdevenv-13ik2dk36zo@rdevel-rdevenv-13ik2dk36zo.ssh.ws-eu116.gitpod.io'
- In Positron Settings, search "remote host" and check the box under "Positron: Remote Host Experimental".
- From the command palette, select Remote-SSH: Connect to Host. When prompted, enter the user@hostname in the SSH command copied from Gitpod, e.g.
rdevel-rdevenv-13ik2dk36zo@rdevel-rdevenv-13ik2dk36zo.ssh.ws-eu116.gitpod.io
- From the explorer, select Open folder, when prompted, enter
workspace/r-dev-env
. The environment variables are set as expected and the remote folder opens as a usual folder, so we can easily open the remote files
The open questions are:
Some open questions:
- Can we open straight in the correct folder? (
workspace/r-dev-env
) - How much of the tutorials will still work? (We expect that the scripts to update R won't work as Positron doesn't use an R terminal the same way as VS code.)
- Assuming we can build R, is there a way we can get Positron to find it, to run in the Positron console?
The last question is the most crucial for us to be able to make this a user-friendly option. But it could still be interesting to be able to build R in the terminal and work with the built R there, whilst being able to edit test/source files in Positron.