quarto-dev / quarto-dev/quarto-cli

Some engine combinations trigger unexpected tlmgr updates

Open
#8,686 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Bug description

Using

-M pdf-engine:latexmk -M pdf-engine-opt:-outdir=/tmp/out

without first disabling the built-in engine with latex-auto-mk: false triggers:

Rendering PDF
running latexmk - 1
  Rc files read:
    NONE
  Latexmk: Nothing to do for 'test.tex'.
  
  
updating tlmgr

updating existing packages

I admit this is a weird combination of options, but a quite similar one is given in the documentation:

pdf-engine: lualatex
pdf-engine-opt: -outdir=out

So perhaps this should be clarified in the documentation, rejected from the command line or made to work somehow.

Steps to reproduce

For a dummy test.qmd document run:

quarto render test.qmd -t pdf -M pdf-engine:latexmk -M pdf-engine-opt:-outdir=/tmp/out

Then try it again disabling the built-in builder:

quarto render test.qmd -t pdf -M latex-auto-mk:false -M pdf-engine:latexmk \
    -M pdf-engine-opt:-outdir=/tmp/out
Expected behavior

If this is not expected to work, clarify it in the documentation and rejected the combination from the CLI. Otherwise make it work properly. It shouldn't start any updating process.

Actual behavior

Shown above.

Your environment

macOS Sonoma

Quarto check output
Quarto 1.4.549
[✓] Checking versions of quarto binary dependencies...
      Pandoc version 3.1.11: OK
      Dart Sass version 1.69.5: OK
      Deno version 1.37.2: OK
[✓] Checking versions of quarto dependencies......OK
[✓] Checking Quarto installation......OK
      Version: 1.4.549
      Path: /Users/carlos/.venvs/base/lib/python3.11/site-packages/quarto_cli/bin

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

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

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

[✓] Checking Python 3 installation....OK
      Version: 3.11.7
      Path: /Users/carlos/.venvs/base/bin/python3
      Jupyter: 5.7.1
      Kernels: python3

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

[✓] Checking R installation...........OK
      Version: 4.3.2
      Path: /opt/homebrew/Cellar/r/4.3.2/lib/R
      LibPaths:
        - /Users/carlos/.rlibs/base
        - /Users/carlos/Documents/Util
        - /opt/homebrew/lib/R/4.3/site-library
        - /opt/homebrew/Cellar/r/4.3.2/lib/R/library
      knitr: 1.45
      rmarkdown: 2.25

[✓] 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

Start with the alternate PDF engine documentation and reproduce the two quarto render commands using pdf-engine, pdf-engine-opt, and latex-auto-mk. Trace how these options select the LaTeX builder and trigger tlmgr; done means the combination no longer starts an update process, or the documentation and CLI clearly reject or explain it.

Written by the indexing model from the issue text.

Assessment

Tech stack
latex
Domain
cli, documentation
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.