quarto-dev / quarto-dev/quarto

Run R cells in vscode using jupyter

Open
#204 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
645
Forks
62
Avg merge
17h 42m
Merged PRs (30d)
13

Description

When executing a {python} cell in vscode it automatically starts a jupyter kernel and console.
When executing a {r} cell, it instead relies on the vscode R extension to start a console.
I would prefer R cells to be executed via jupyter as well, using an R kernel.

This is mostly for two reasons:

  • The jupyter extension makes it really easy to work with different virtual environments. I can simply add a different kernel for each environment. I haven't found a way of specifying a virtual R environment in the vscode R extension except for manually setting paths in the configuration.
  • the jupyter console looks and feels much nicer (even compared to radian) and I'm more used to it.

Contributor guide

No contributing guide indexed for this repository

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 or tests. Start by tracing VS Code cell execution and the existing Jupyter and R-extension integrations; done means R cells launch through a Jupyter R kernel and allow the environment or kernel selection described in the issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
jupyter, r, vscode
Domain
developer-experience, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.