-
Notifications
You must be signed in to change notification settings - Fork 5
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
How to debug errors in PDF log compilation? #64
Comments
Although this sounds like a pandoc issue, |
Good question; I have no idea where Pandoc writes the temporary LaTeX file. What you can do is change the call to Pandoc yourself. Insert target_file = "#{ParameterManager.instance[:jobname]}.log.tex above that line and you should get the LaTeX file. If you manage to construct an MWE, I'll have a look myself. FWIW, Note to self: this may be more robust if the markdown log used fenced code blocks instead of indented code blocks. Note to self 2: since this keeps popping up, maybe log compilation should be done in two steps, always: Pandoc creates |
Think, a MWE will be difficult to construct. Maybe on a rainy day. 😃 Current investigation result. The first occurrence of
But there is no \blockitem before. |
There should be a A good approach to creating MWEs is to delete half of the code and see if the error persists. If yes, continue. If no, undo and delete the other half. |
Deferred to #77 after inspecting a concrete example (private communication). Hotfix for the specific issue may happen, though, pending further input. |
…via MD. Should also fix #64 along the way. * Writing hashes is a bit more robust now: only write if there are any hashes.
@koppor I completely reimplemented LaTeX/PDF log generation. If you are still interested, give it a shot -- there should be no (or other, at least) problems now. |
Creation of the pdf logs (parameter
-lf pdf
) fails here. The content ofdocument.log.pdf.log
is as follows:I was searching for
document.log.tex
, but there was onlydiss-kopp.log.md
. Where can I find the.tex
to dig a bit into possible causes for the above error message?The text was updated successfully, but these errors were encountered: