quarto-dev / quarto-dev/quarto
Quarto extension doesn't watch inputs when previewing in web-based VSCode instance (code-server)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 645
- Forks
- 62
- Avg merge
- 17h 42m
- Merged PRs (30d)
- 13
Description
This web-based VSCode instance I'm using runs on a proprietary platform which cannot show quarto previews in an internal window. That is fine, the platform itself has a feature to expose opening ports in separate browser tabs, so I can open a tab with the quarto preview once quarto sets up that network connection.
What's weird, though, is that quarto seems to always set --no-watch-inputs in the terminal that opens, for example:
quarto preview /home/jrun/data/code/test.qmd --no-browser --no-watch-inputs
I'm finding no available setting in the extension to control watching behavior for previews, but from a local VSCode I'm used to the watching-by-default behavior.
If I run quarto's terminal command myself without the --no-watch-inputs, watching works fine and the separate tab with the preview updates as expected.
Quarto extension version: v1.115.0
code-server: v4.23.0
Code: 1.88.0
Commit: 0cca7c67a4aba0e8ce199df0fdc59b64fc659fbc
Date: 2024-04-05T22:24:44.781Z (5 mos ago)
Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:127.0) Gecko/20100101 Firefox/127.0
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
Reproduce the preview in the reported code-server and VS Code versions, then inspect how the Quarto extension constructs the terminal command. Confirm the behavior with and without --no-watch-inputs; done means web-based previews watch input changes or provide a way to control that behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vscode
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100