How to output pdf?

[faurehu]

I'd like to test the pdf output. What command can I call to run the latex compiler?

[jheer]

In your article YAML metadata/header block, you can add latex: true (or more detailed latex options) underneath the output key.

Here are some examples:

• https://github.com/uwdata/living-papers/blob/main/examples/fast-kde/fast-kde.md?plain=1#L23
• https://github.com/uwdata/living-papers/blob/main/examples/reactive/reactive.md?plain=1#L8

[faurehu]

Thank you! Best, Matias Faure PhD student - NYU Politics

…

On Oct 25, 2023 at 11:30 PM -0400, Jeffrey Heer ***@***.***>, wrote: In your article YAML metadata/header block, you can add latex: true (or more detailed latex options) underneath the output key. Here are some examples: • https://github.com/uwdata/living-papers/blob/main/examples/fast-kde/fast-kde.md?plain=1#L23 • https://github.com/uwdata/living-papers/blob/main/examples/reactive/reactive.md?plain=1#L8 — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>

[GdSAu]

@jheer, hello.
I tried setting output: latex: true, and i get the following error:
Compiling latex PDF Error: ENOENT: no such file or directory, lstat '.temp/latex/index.pdf'
Any idea?
Thanks in advance

[jheer]

@GdSAu I would need more information to diagnose the issue. When generating a latex PDF, Living Papers writes the latex project to .temp/latex/ and runs pdflatex and bibtex within that directory. It then copies the generated PDF out of the folder. It looks like this final copy is what is breaking? So I'd recommend first checking the contents of .temp/latex/. There should be a latex log files which you can check to see if perhaps there was an error during latex compilation...