quarto-dev / quarto-dev/quarto
VS Code extension: quarto.path does not have any impact.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 645
- Forks
- 62
- Avg merge
- 17h 42m
- Merged PRs (30d)
- 13
Description
I have expanded the quarto RHEL 7 tarball to my home directory, and thought I could just tell VS Code quarto extension to use it from there, rather than change my shell PATH to include this custom quarto path.
So, I have set quarto.path. But when I run say, quarto preview from the VS Code command pallet, I can see the command it sends to the terminal window and it is just:
quarto preview ...
No sign of it using the quarto.path setting I have set.
This is with VS Code Remote, so the Quarto extension is installed on the remote SSH machine (and the setting is changed in the Remote settings.)
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
No files or tests are named. Start by locating the VS Code extension's handling of the quarto.path setting and reproduce the command-palettte preview flow in a Remote SSH window. Done means the configured path is used when launching quarto preview instead of relying only on PATH.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100