REditorSupport / REditorSupport/vscode-R

Gotcha for people with `conda`

Open
#689 7 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
TypeScript
Stars
1.2k
Forks
139
Avg merge
2h 46m
Merged PRs (30d)
5

Description

I recently discovered a bug that occurs for people with conda installations using radian -- if one has conda installed for python packages, VS code actively recommends using the "terminal.integrated.inheritEnv": false setting (it has a popup, then adds if you click yes).

BUT

that results in vscode-R not being able to find RHOME, and so if I launch radian, I get this error (it just flashes up for a moment -- had to screen record to see it -- they terminal closes, and I get a The terminal process "/Users/Nick/miniconda3/bin/radian" terminated with exit code: 1. popup:

image

I set my R_HOME var in both zsh and bash profiles, and if I open a zsh terminal in VSCode, radian works, and if I open a bash terminal in VSCode, radian works. It's only when it's launched by trying to run an R file that I have a problem.

Adding this to settings:

    "terminal.integrated.env.osx": {
        "R_HOME": "/Library/Frameworks/R.framework/Resources/"
    }

(based on advice in #431) fixes the problem.

Contributor guide

Open the contributing guide

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

No source file or test is named. Reproduce the issue by launching radian through an R file with terminal.integrated.inheritEnv set to false, compare it with the working shell launches and the R_HOME workaround from #431, and define done as successful launch without requiring that workaround.

Written by the indexing model from the issue text.

Assessment

Tech stack
r, typescript, vscode
Domain
developer-experience, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.