Issue running code line-by-line in vscode: Cannot determine RHOME
See original GitHub issueDescribe the bug
Hi! I’m getting an error of Cannot determine R HOME when trying to execute code line-by-line in VSCode. This is a new problem which hadn’t happened to me before, so I think an update might have broken some settings in some weird and wonderful way?
To Reproduce Steps to reproduce the behavior:
- Open a random R script
- command + enter on the first line (which happens to say
library(tidyverse)but this is irrelevant)
Do you want to fix by self?
I wish I could
(If yes,) what kind of help do you want? (e.g. Which file should I fix, Survey (related documents)
(If related)setting.json
// R path for Mac OS X
"r.rterm.mac": "/Users/darya/anaconda3/bin/radian"
// R command line options (i.e: --vanilla)
"r.rterm.option": [],
// An optional encoding to pass to R when executing the file, i.e. 'source(FILE, encoding=ENCODING)'
"r.source.encoding": "UTF-8",
// Keeping focus when running
"r.source.focus": "editor",
// Use active terminal for all commands, rather than creating a new R terminal
"r.alwaysUseActiveTerminal": false,
// Use bracketed paste mode
"r.bracketedPaste": true,
// Enable R session watcher (experimental)
"r.sessionWatcher": true,
// Delay in milliseconds before sending each line to rterm (only applies if r.bracketedPaste is false)
"r.rtermSendDelay": 8,
Expected behavior I was hoping the code would run line by line…
Environment (please complete the following information):
- OS: macOS 10.15.7 (19H2)
- VSCode Version: Version: 1.50.1
- R Version: 4.0.2
- vscode-R version: v1.5.1
Additional context
Running /Users/darya/anaconda3/bin/radian (or radian) from the zsh command line results in R happily launching, and the library(tidyverse) code working without errors (as does running the script from RStudio)
What’s wrong with my Config? Thanks in advance!
PS I have seen the issue here - but can’t seem to fix the R RHOME issue by using the tips there.
Issue Analytics
- State:
- Created 3 years ago
- Comments:14 (8 by maintainers)

Top Related StackOverflow Question
@dvanic Maybe you need to specify the following in your vscode settings?
This issue was closed because it has been inactive for 14 days since being marked as stale.