quarto-dev / quarto-dev/quarto-cli

Disabling latex-auto-mk produces corrupted pdf

Open
#9,016 7 comments 0 reactions 1 assignee View on GitHub

@cderv is already working on this.

Since Mar 8, 2024.

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

Description

Bug description

No matter the engine configuration, when I disable latex-auto-mk I always get a pdf file that I cannot open in any viewer. Instead, when latex-auto-mk is enabled the pdf renders correctly.

Steps to reproduce

For example, for an input:

test.md

foobar

I have run quarto render test.md -t pdf with the following configurations:

_quarto.yaml

title: "foobar"
latex-auto-mk: false
_quarto.yaml

title: "foobar"
latex-auto-mk: false
pdf-engine: pdflatex
_quarto.yaml

title: "foobar"
latex-auto-mk: false
pdf-engine: xelatex
_quarto.yaml

title: "foobar"
latex-auto-mk: false
pdf-engine: latexmk
pdf-engine-opts:
  - '-auxdir=/tmp/quarto-aux'
  - '-emulate-aux-dir'
Expected behavior

A well-formed pdf is produced.

Actual behavior

This is what Preview shows for the resulting output:

image
Your environment

OS: macOS Sonoma 14.3.1

Quarto check output
Quarto 1.4.550
[✓] 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.550
      Path: /private/tmp/qenv/lib/python3.11/site-packages/quarto_cli/bin

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

[✓] Checking LaTeX....................OK
      Using: Installation From Path
      Path: /Library/TeX/texbin
      Version: 2023

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

[✓] Checking Python 3 installation....OK
      Version: 3.11.8
      Path: /private/tmp/qenv/bin/python3
      Jupyter: 5.7.1
      Kernels: python3

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

[✓] Checking R installation...........OK
      Version: 4.3.3
      Path: /opt/homebrew/Cellar/r/4.3.3/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.3/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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.