quarto-dev / quarto-dev/quarto

VS Code Extension: Preview ignores `output-dir` in `_quarto.yml`

Open
#375 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Until recently the VS Code Extension put the files it generated for a preview (for revealjs) in the directory which I specified in _quarto.yml in output-dir.

Now this behaviour changed:

  • the extension ignores the value in output-dir
  • it creates instead a separate directory with the name MyFile_files for a preview of MyFile.qmd

Is there any way to get the former behaviour back? Is it possible to specify the output directory for the preview explicitly?

I'm using Quarto 1.4.549 and the VS Code Extension v1.110.1

BTW, there is another strange behaviour within this context:

  • When I render the whole project (using quarto render --to revealjs) after showing a preview, then the content of the preview window changes and shows the content of output-dir instead of MyFile_files
  • But as soon as the "Preview"-button in VS Code is used again, the preview window switches back to the content of MyFiles_files

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 VS Code preview behavior with Quarto 1.4.549 and VS Code Extension v1.110.1, using a project whose _quarto.yml sets output-dir and a MyFile.qmd revealjs document. Compare the preview output with quarto render --to revealjs and determine whether the preview should honor output-dir; done means repeated previews consistently use the configured directory.

Written by the indexing model from the issue text.

Assessment

Tech stack
vscode
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.