quarto-dev / quarto-dev/quarto

Positron: Render on Save button applies at project level

Open
#723 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Bug description

Checking the "Render on Save" checkbox applies it to all documents in a project. That is, checking the box in one open file, checks it for any other files in the project.

It may be this is the desired behavior (i.e. it is equivalent to checking the setting Quarto > Render: Render on Save), however, it is not the default behavior in RStudio. In RStudio the checkbox with the same name behaves more like setting render-on-save in the document header:

---
editor:
  render-on-save: true
---

If the current behavior is indeed the desired behavior, this needs to be clarified in the docs on quarto.org, which I am happy to do.

Steps to reproduce

Create test-project

quarto create project default test-project test-project

In test-project/

touch other.qmd

Check box for "Render on Save" in other.qmd.

Actual behavior

Box for "Render on Save" is also now checked in test-project.qmd.

Expected behavior

Based on RStudio behavior, Box for "Render on Save" in test-project.qmd should remain unchecked.

Your environment
  • Positron Version: 2025.06.0 (Universal) build 145
  • Quarto extension 1.122.0

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

Start by reproducing the behavior in the generated test-project with test-project.qmd and other.qmd, following the listed Positron and Quarto extension versions. Trace how the Render on Save checkbox is stored and determine whether it should remain document-specific like the expected behavior; if project-level behavior is intentional, the docs need clarification instead.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
developer-experience, frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.