quarto-dev / quarto-dev/quarto
Quarto regularly renders the wrong document
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 645
- Forks
- 62
- Avg merge
- 17h 42m
- Merged PRs (30d)
- 13
Description
I've been having a consistent issue with the Quarto VSCode plugin since I started using it a month or two ago where, instead of rendering the requested document, it re-renders a document I was working on earlier. I usually need to ask it to render the document several times before it will update to rendering the new one.
I'm not sure if this is a bug or just an opaque way that it decides what to render. If it's the former, here's my bug report. If it's the latter, how do I direct its attention properly?
For example, here is my set of open tabs in VScode; both have Quarto YAMLs:
I rendered the human_capital file earlier. Now, I am focused on the Distributor Notebook file. I have clicked on one of the code chunks to try to emphasize that this is indeed the tab I want to have focus. Then I use the three-dots menu and select "Render."
The first time I do this, it renders the human_capital file once again. The second time I do this, without making any other changes, it successfully renders Distributor Notebook.
Thank you!
Windows 10
VScode 1.79.2
Quarto plugin 1.88.0
Quarto 1.3.433 (although this was also happening before I updated Quarto)
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 reproducing the issue in VS Code on Windows 10 with two open Quarto documents, using the listed VS Code, plugin, and Quarto versions. Compare the focused document with the document selected by the three-dots Render command; done means the focused document renders on the first attempt.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100