REditorSupport / REditorSupport/vscode-R

Conda activate before running the terminal

Open
#1,405 1 comment 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

We have two ways to activate radian, but it seems they are not the same, is it because the first method does not activate the conda envs, but apparently the second method has two more steps.
image

image

image

This is my settings.json

[
    "r.bracketedPaste": true,
    "r.plot.useHttpgd": true,
    "r.rpath.linux": "/home/toxin/anaconda3/envs/r431/bin/R",
    "r.rterm.linux": "/home/toxin/anaconda3/envs/r431/bin/radian",
    "r.rterm.option": [
        "--no-site-file",
        "--r-binary=/home/toxin/anaconda3/envs/r431/bin/R"
]

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

Start with the issue's settings.json and compare the two documented ways of activating radian in the attached screenshots. Reproduce the behavior with the listed R and radian paths in a Linux Conda environment, then trace the terminal activation entry point in the vscode-R extension. Done means the difference between the methods and the required Conda activation behavior are documented or consistently corrected.

Written by the indexing model from the issue text.

Assessment

Tech stack
anaconda, 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
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.