REditorSupport / REditorSupport/vscode-R
Did anything change w.r.t. `R_HOME` and `radian` recently?
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.2k
- Forks
- 139
- Avg merge
- 2h 46m
- Merged PRs (30d)
- 5
Description
I noticed that the command to start a new R terminal fails now when the --r-binary is set. Did anything change recently that requires to explicitly export the R_HOME variable before invoking radian?
➜ ~ git:(main) ✗ which R
/usr/local/bin/R
➜ ~ git:(main) ✗ which radian
radian: aliased to ~/.python-packages/bin/radian
➜ ~ git:(main) ✗ radian
R version 4.5.1 (2025-06-13) -- "Great Square Root"
Platform: aarch64-apple-darwin20 (64-bit)
r$> q()
➜ ~ git:(main) ✗ radian --r-binary=/usr/local/bin/R
Fatal error: R home directory is not defined
➜ ~ git:(main) ✗ R RHOME
/Library/Frameworks/R.framework/Resources
➜ ~ git:(main) ✗ export R_HOME=$(R RHOME)
➜ ~ git:(main) ✗ radian --r-binary=/usr/local/bin/R
R version 4.5.1 (2025-06-13) -- "Great Square Root"
Platform: aarch64-apple-darwin20 (64-bit)
r$>
I installed R via brew install --cask r-app.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure with radian --r-binary=/usr/local/bin/R, then compare it with the same command after export R_HOME=$(R RHOME). The issue names no repository file or test; done would require determining whether the R/radian launch path should handle this environment and documenting or testing the resulting behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- cli, developer-experience
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100