-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Request: Fully user configurable directory for specifying where to find interpreters #2235
Comments
If the tool's popular, I don't see any reason we couldn't add that to the set of locations we scan ... it isn't expensive to check! Might be more flexible to make this a setting that accepts an array of additional directories to search? Like "positron.r.extraArguments": {
"scope": "window",
"type": "array",
"items": {
"type": "string"
},
"default": [],
"description": "%r.configuration.extraArguments.description%"
}, |
An array sounds good! This is the first time I have ever heard of this tool, but we can add it to the list of places to search as well (i.e. do both things suggested here) |
Explicitly:
|
I'm going to suggest we re-triage this for R, because there's a very long thread of people for whom our automated discovery doesn't work for one reason or another, and just allowing you to tell us where R live would give all of them a way to move forward. |
It would be useful to look at the Python extension's "Select Interpreter" UI experience, which is IMO very good. This could help us with other alternative ways of installing R like conda, pixi, etc. |
@dskard has a case where a tool he uses puts R versions in
~/.renv/
rather than the "standard location" that R (and rig) typically use.Rather than including this as a possible place to look for R, I think we should just add a global option that allows users to specify a location to look for R interpreters in. I imagine this is a setting that lives under
positron-r
, and is just a plain text field corresponding to a directory that we look through.The text was updated successfully, but these errors were encountered: