posit-dev / posit-dev/positron

Cmd + shift + k does not knit an R Markdown document

Open
#3,737 6 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

area: core enhancement lang: r support
Dominant language
TypeScript
Stars
4.3k
Forks
184
Avg merge
1d 9h
Merged PRs (30d)
195

Description

Positron Version:

Positron Version: 2024.06.1 (Universal) build 27
Code - OSS Version: 1.90.0
Commit: https://github.com/posit-dev/positron/commit/a893e5b282612ccb2200102957ac38d3c14e5196
Date: 2024-06-26T02:08:06.673Z
Electron: 29.4.0
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Darwin arm64 23.4.0

Steps to reproduce the issue:

  1. Create an Rmd file
  2. hover over the play button to assert that the keyboard shortcut should be available
image
  1. Press keyboard shortcut to try rendering Rmd
  2. assert that nothing happens

What did you expect to happen?

The document would render.

Additional thoughts on this:

I find this behavior to be really awkward and I think the story can be improved greatly if Positron and quarto extension didn't classify Rmd files as Quarto language type.

image

If Rmd is recognized for an Rmd document you can create keybindings that utilize something like

       "args": {
            "langId": "rmd",
            "code": "rmarkdown::render(...)"
        }

Forcing Rmd to be quarto makes everything uncomfortable.

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

Reproduce the issue with an R Markdown file in Positron and inspect the play-button command and keyboard-shortcut handling, including how Rmd is classified as Quarto. Done means Cmd+Shift+K triggers rendering and the shortcut shown by the play button matches the working command.

Written by the indexing model from the issue text.

Assessment

Tech stack
r
Domain
developer-experience, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 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.