Skip to content
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

Open
DavisVaughan opened this issue Feb 8, 2024 · 6 comments

Comments

@DavisVaughan
Copy link
Contributor

@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.

@jmcphers
Copy link
Collaborator

jmcphers commented Feb 8, 2024

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 extraArguments:

        "positron.r.extraArguments": {
          "scope": "window",
          "type": "array",
          "items": {
            "type": "string"
          },
          "default": [],
          "description": "%r.configuration.extraArguments.description%"
        },

@DavisVaughan
Copy link
Contributor Author

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)

@jennybc
Copy link
Member

jennybc commented Feb 12, 2024

Screenshot 2024-02-12 at 9 42 01 AM

Let's discuss this in relation to this existing configuration element that's already available. I can imagine how it's not the same / not enough, but let's just spell it out.

@DavisVaughan
Copy link
Contributor Author

Explicitly:

  • The Kernel Path referred to there is "Where do we find ARK?". There is only ever exactly 1 place where this should be. Most users won't have to care about this, because ark is bundled in release positron and positron knows how to find it. But I can imagine it can be useful sometimes to point to a debug version of ark in a release build of positron.
  • We want a separate option for, "Where do we find R installations?". There can be >1 places where R installations live, especially on Linux. We try reasonably hard to search for R installations on Mac, Windows, and Linux in "known" locations, but we will ultimately miss someone's esoteric setup at some point, so providing an option that accepts an array of paths to search for R installations in seems reasonable.

@jmcphers
Copy link
Collaborator

jmcphers commented Aug 15, 2024

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.

#3677

@juliasilge
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants