I'm using Pandoc 1.16 on OS X 10.11.2 installed via the OS X binary. I'm trying to convert a Markdown file to PDF, and I'm supplying a custom LaTeX engine via --latex-engine.
Here's what I entered at the command line to produce the error.
~$ echo "Hello world" > test.md
~$ which pdflatex
/Library/TeX/texbin/pdflatex
~$ pandoc test.md -o test.pdf --latex-engine=/Library/TeX/texbin/pdflatex
Unknown program /Library/TeX/texbin/pdflatex
pandoc: Error producing PDF
~$ echo $?
43
This appears to be a regression from Pandoc 1.15.2, since the same commands produce the expected output when I install that version.
[1]@jgm Could you provide a patch release for this bug at your earliest
convenience? It has affected quite a few R Markdown users. Thanks!
—
Reply to this email directly or [2]view it on GitHub.
References
1. https://github.com/jgm
2. #2618 (comment)
PS. You could fix this in R Markdown by simply adding the
path to the latex program to PATH in the local environment
in which pandoc is run, and using the basename instead of
the fully qualified path in --latex-engine.
+++ Yihui Xie [Jan 08 16 13:13 ]:
[1]@jgm Could you provide a patch release for this bug at your earliest
convenience? It has affected quite a few R Markdown users. Thanks!
—
Reply to this email directly or [2]view it on GitHub.
References
1. https://github.com/jgm
2. #2618 (comment)
Yeah, I know we can fix it in R Markdown, but our problem is that it is not easy for us to make a new release soon (due to the restrictions of CRAN). Thanks very much!
c-forster
pushed a commit
to c-forster/pandoc
that referenced
this issue
I'm using Pandoc 1.16 on OS X 10.11.2 installed via the OS X binary. I'm trying to convert a Markdown file to PDF, and I'm supplying a custom LaTeX engine via
--latex-engine.Here's what I entered at the command line to produce the error.
This appears to be a regression from Pandoc 1.15.2, since the same commands produce the expected output when I install that version.