Did anything change w.r.t. `R_HOME` and `radian` recently?

[mihaiconstantin]

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.

[xuestrange]

Can't start radian in vscode (via command R: create R terminal)on MacOS when the --r-binary and r.rterm.mac are set. The error message "Cant determine R HOME" pops up. This bug appeared after a major update of a vscode (1.105.1 i guess). I also found that radian can be started via terminal (create a terminal in vscode, then type radian).

Did someone meet similar bug?

BTW, some useful info: R4 .5.1, MacOS 15.7.1, radian 0.6.15