quarto-dev / quarto-dev/quarto-cli

Exit with code 1 when running `quarto render --quiet <file>`?

Open
#13,326 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
JavaScript
Stars
6k
Forks
458
Avg merge
1d 9h
Merged PRs (30d)
41

Description

I have:
  • searched the issue tracker for similar issues
  • installed the latest version of Quarto CLI
  • formatted my issue following the Bug Reports guide
Bug description

When rendering with --quiet flag, the exit code is always 1 even when it succeeds.

Steps to reproduce
  1. Create any Quarto file (can even be empty)
  2. Run quarto render --quiet file.qmd
  3. The exit code is 1
Actual behavior

No response

Expected behavior

If it succeeds, a 0 exit code should be given.

Your environment

macOS Tahoe Public Beta. Quarto CLI

Quarto check output
Quarto 1.7.34
[✓] Checking environment information...
      Quarto cache location: /Users/sghuang/Library/Caches/quarto
[✓] Checking versions of quarto binary dependencies...
      Pandoc version 3.6.3: OK
      Dart Sass version 1.85.1: OK
      Deno version 1.46.3: OK
      Typst version 0.13.0: OK
[✓] Checking versions of quarto dependencies......OK
[✓] Checking Quarto installation......OK
      Version: 1.7.34
      Path: /Applications/quarto/bin

[✓] Checking tools....................OK
      TinyTeX: v2025.08.02
      Chromium: (not installed)

[✓] Checking LaTeX....................OK
      Using: TinyTex
      Path: /Users/sghuang/Library/TinyTeX/bin/universal-darwin
      Version: 2025

[✓] Checking Chrome Headless....................OK
      Using: Chrome found on system
      Path: /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
      Source: MacOS known location

[✓] Checking basic markdown render....OK

[✓] Checking Python 3 installation....OK
      Version: 3.13.5 (Conda)
      Path: /Users/sghuang/.local/share/mamba/envs/ds/bin/python
      Jupyter: 5.8.1
      Kernels: python3, ds

[✓] Checking Jupyter engine render....OK

[✓] Checking R installation...........OK
      Version: 4.5.1
      Path: /Library/Frameworks/R.framework/Resources
      LibPaths:
        - /Library/Frameworks/R.framework/Versions/4.5-arm64/Resources/library
      knitr: 1.50
      rmarkdown: 2.29

[✓] Checking Knitr engine render......OK

Contributor guide

Open the contributing guide

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

Reproduce the issue with quarto render --quiet file.qmd and compare its exit status with a normal render. Trace the CLI entry point and the handling of --quiet to find why successful rendering returns 1. Done means successful quiet renders return 0, with a regression test covering the command.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 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.