quarto-dev / quarto-dev/quarto
VS Code: Generic code cell execution
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 645
- Forks
- 62
- Avg merge
- 17h 42m
- Merged PRs (30d)
- 13
Description
Currently, the VS Code extension only allows interactive code execution (for .qmd files) for a few specified languages. The question has been raised whether that could be enabled for all languages Quarto otherwise supports via Jupyter or knitr.
Not sure what can be done, especially because there is so many options of interactive available when you consider all available Jupyter Kernel, and custom knitr engine. Should quarto extension know them all to activate the run cell button ? Maybe there is a way that does not imply to know them all if an other extension can communicate support.
Originally posted by @cderv in https://github.com/quarto-dev/quarto-cli/discussions/4757#discussioncomment-11140994
Although the docs do not yet reflect this, Stata "Run Cell" was added in https://github.com/quarto-dev/quarto/commit/5e0c7b5af4d23211d9028d31536c9a63b79a977e (see https://github.com/quarto-dev/quarto/issues/336#issuecomment-1873437072). Also supported currently: bash (with "sh" and "shell" as aliases).
Would it make sense to likewise add code execution for all languages already recognized here and/or here?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading apps/vscode/src/vdoc/languages.ts and packages/editor-core/src/languages.ts, then inspect the VS Code extension's existing Run Cell support for Stata and bash. Compare the languages recognized there with the current execution integrations and related documentation. Done means a decided, tested approach for enabling generic execution without requiring the extension to enumerate every available kernel or knitr engine.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jupyter, typescript, vscode
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100