quarto-dev / quarto-dev/quarto-cli

Manuscripts -- `notebooks:` mask `render:` property in _qarto.yml

Open
#11,084 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Bug description

There is a very weird behaviour in Manuscripts. Consider the following _quarto.yml file

project:
  type: manuscript
  execute-dir: project
  render:
    - "notebooks/analyse_hypothesis.Qmd"

manuscript:
  article: index.qmd
  # notebooks:
  #   - notebook: notebooks/cars-plot.Qmd
  #     title: "hypothesis analysis"
  #     download-url: notebooks/cars-plot.Qmd

currently notebooks/analyse_hypothesis.Qmd and index.qmd are rendered. If I uncomment the notebooks section then notebooks/analyse_hypothesis.Qmd is no longer rendred (despite mentioning it explicitly).


side note: when I manually execute quarto render notebooks/analyse_hypothesis.Qmd --to html it gets executed in the directory notebooks which contradicts the execute-dir: project. Is this expected behavior?

Steps to reproduce

No response

Expected behavior

No response

Actual behavior

No response

Your environment

Quarto: 1.5.57

Quarto check output
Quarto 1.5.57
[✓] Checking versions of quarto binary dependencies...
      Pandoc version 3.2.0: OK
      Dart Sass version 1.70.0: OK
      Deno version 1.41.0: OK
      Typst version 0.11.0: OK
[✓] Checking versions of quarto dependencies......OK
[✓] Checking Quarto installation......OK
      Version: 1.5.57
      Path: /opt/quarto/bin

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

[✓] Checking LaTeX....................OK
      Using: Installation From Path
      Path: /usr/bin
      Version: undefined

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

[✓] Checking Python 3 installation....OK
      Version: 3.12.7
      Path: /usr/bin/python3
      Jupyter: (None)

      Jupyter is not available in this Python installation.
      Install with python3 -m pip install jupyter

[✓] Checking R installation...........OK
      Version: 4.4.1
      Path: /usr/lib64/R
      LibPaths:
        - /home/lukas/Work/LentilOatMixedCropping/renv/library/linux-arch-rolling/R-4.4/x86_64-pc-linux-gnu
        - /home/lukas/.cache/R/renv/sandbox/linux-arch-rolling/R-4.4/x86_64-pc-linux-gnu/9a444a72
      knitr: 1.48
      rmarkdown: 2.28

[✓] 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 behavior with _quarto.yml, notebooks/analyse_hypothesis.Qmd, and index.qmd, first checking the render command described in the issue. Compare results with and without the manuscript.notebooks section, and also check the execute-dir: project behavior when rendering the notebook directly. Done means the explicit project.render entry remains rendered and the execution-directory behavior is explained or corrected.

Written by the indexing model from the issue text.

Assessment

Domain
build-system, cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.