New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Debugging Options] For converting to PDF: improve debugging options #1653
Comments
Why not just output to latex format? |
You would want the -s flag as well.
|
@mszep: That's what I usually do. But it takes more time to match the exact settings when using longer, komplex command line options with PDF conversion. It would be faster to immediately have Pandoc telling me the location of the intermediate files by adding a simple additional flag to the command... |
I know where you're coming from; in practice I tend to use use makefiles containing a call to My feeling is that pandoc's direct pdf export is geared towards people who don't know and don't want to learn latex. Anyone else is probably better off exporting to latex, and taking care of compilation to pdf themselves. |
Great! Thanks a lot, John. |
When converting to PDF,
pandoc
should allow (via a commandline switch such as--pdfdebug
or similar) to preserve (or dump) the intermediate LaTeX code somewhere on the harddisk and issue a message where the *.tex (and maybe other log and auxiliary files from{pdf,lua,xe}latex
runs) may be found.The text was updated successfully, but these errors were encountered: