posit-dev / posit-dev/mcp-repl

`R_HOME` is more for introspection than configuration

Open
#44 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
70
Forks
5
PR merge metrics
No merged PRs in 30d

Description

I'm pretty intrigued by this project! I saw it in use during Hadley's recent data science hangout.

So I came to look at the README so I can try it out.

I've done a lot of work on R runtime discovery in Positron and one thing I read caught my eye:

https://github.com/posit-dev/mcp-repl#r-interpreter-which-r-installation-is-used

To force a specific R installation, set R_HOME in the environment that launches mcp-repl.

We've occasionally seen folks trying to use R_HOME like this in Positron's issues and it generally leads to frustration. While trying to understand those situations, I've had to read up on what R_HOME is designed to do and I think this is basically fighting against the intent of R_HOME:

https://github.com/posit-dev/positron/issues/12278#issuecomment-4001245549

TL;DR

My impression is that R_HOME is intended to be a env var you can consult once you've launched and R version to ask it "where do you live?" It's not something one sets and then expects that to drive the usage of a specific R installation.

I just thought this might be worth some 🤔

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the README section "R interpreter: which R installation is used" and the linked discussion about R_HOME. Determine whether the guidance should be revised to reflect the reported behavior, then verify that the README clearly explains how an R installation is selected.

Written by the indexing model from the issue text.

Assessment

Tech stack
r
Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.