quarto-dev / quarto-dev/quarto

output_dir ignored in VSCode

Open
#640 1 comment 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

I can't get to save my output files in my folder of preference. Here's a MWE:

  1. create a new file test.qmd in the folder Folder
  2. add the following:
---
format:
  html:
    output-dir: "HTML files"
  pdf:
    output-dir: "pdf_files"
---
Hi there

Then, a file Folder/test.html is created (expected behaviour was to create Folder/HTML files/test.html)

No pdf file is created whatsoever.

A folder test_files is also created with the following:

Image

I am using Quarto v. 1.5.57 and VSCode 1.96.4

https://github.com/quarto-dev/quarto/issues/375#issue-2129065114 here's a similar issue. Although not exactly the same one, could be related

How can I get quarto to save the output files to my subfolder of preference? Note that I want this behaviour to be document-specific and format-specific, so I don't think I can do this from my _quarto.yml project file...

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 issue with the mentioned test.qmd file in VSCode using Quarto 1.5.57, including both format-specific output-dir settings. Trace how VSCode handles those settings and compare the generated paths with the expected HTML and PDF locations; done means each format is written to its configured subfolder and no unintended test_files folder is created.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, vscode
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.