REditorSupport / REditorSupport/vscode-R

Use separate R-process per file/syntax

Open
#180 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

  • VSCode Version: 1.41.1
  • VSCode-R Version: 1.20
  • OS Version: Windows 10

Thank you for this great extension. I'm a statistician and not a programmer, and I'd like to make a suggestion. If this is inappropriate, please direct me to the best channel for asking and delete the "issue".

I'd like to use a separate R-process (Terminal) for every file, so this workflow is possible:

  1. Open R file and run source
  2. Open another R-File. Run line or run source opens another terminal with an isolated R-process

Goal is to work on two or more syntax files within a project in parallel.

With the option "use active terminal" this is somehow already possible, but switching requires to switch the syntax and to the respective terminal, the "pairs" have to be remembred and if one doen't pay attention, a command could be sent to the wrong process.

Is this already possible somehow or could such an option be implemented?

Thank you.

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

The issue names no files, tests, or entry points. Start by locating VSCode-R's handling of R terminals and the existing "use active terminal" option; done means each file can run commands in its own remembered R process without switching terminals manually.

Written by the indexing model from the issue text.

Assessment

Tech stack
r, typescript
Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.