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, Positron saves a very exact version of R used with each workspace (as the "affiliated runtime"), and attempts to restore it when the workspace is started up.
However, in many (most?) situations, the desire isn't necessarily to use that very specific version of R. R users are accustomed to using RStudio, which just picks up whatever's current.
Proposal: Allow Positron workspaces to bind to R in such a way that they can use whatever the current version is without any fuss/warnings.
We could do this with changes only to the R language pack:
When building R language metadata, we add a flag to the "additional fields" (alongside the home path and bin path) indicating whether the version of R is the current default on the machine.
When Positron asks the R language pack to validate metadata, it checks to see if the R version being sought was the current version when the metadata was saved. If it is, the R language pack returns updated metadata corresponding to the new current R version, if it has changed.
Currently, Positron saves a very exact version of R used with each workspace (as the "affiliated runtime"), and attempts to restore it when the workspace is started up.
However, in many (most?) situations, the desire isn't necessarily to use that very specific version of R. R users are accustomed to using RStudio, which just picks up whatever's current.
Proposal: Allow Positron workspaces to bind to R in such a way that they can use whatever the current version is without any fuss/warnings.
We could do this with changes only to the R language pack:
Related to (and perhaps an enhancement of) #2316.
The text was updated successfully, but these errors were encountered: