posit-dev / posit-dev/positron
Command-Return in quarto document doesn't execute
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 4.3k
- Forks
- 184
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 206
Description
System details:
Positron and OS details:
Positron Version: 2025.05.0 (Universal) build 142
Code - OSS Version: 1.99.0
Commit: 17df8dd67df471d39688fc6cd02e3f23543b4d72
Date: 2025-05-05T15:42:05.662Z
Electron: 34.3.2
Chromium: 132.0.6834.210
Node.js: 20.18.3
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.4.0
Interpreter details:
R 4.5.0
Describe the issue:
When working on a Quarto document, clicking on "Run Cell" correctly executes my R block. But when I select some code within the R block and hit command-return I get the error message: "Cannot execute code because no there is no registered runtime for the 'quarto' language."
This worked previously, but fails now that I've updated to 2025.05.0-142.
Steps to reproduce the issue:
- Open a Quarto document
- Enter a code block with simply
1as the contents. Same behavior for anRblock or apythonblock - Highlight
1and press command-return
Expected or desired behavior:
Selected code executes
Were there any error messages in the UI, Output panel, or Developer Tools console?
"Cannot execute code because no there is no registered runtime for the 'quarto' language."
Contributor guide
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
Reproduce the issue in a Quarto document with an R or Python block containing 1, comparing Run Cell with selecting the code and pressing Command-Return. Trace the command-return execution path and its handling of the quarto language; done means selected code executes without the no-registered-runtime error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, r
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100