Deal gracefully with multiple 'Transcript written on' lines. #60
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Whenever pdflatex is invoked on a clean copy of the texmf, it will first invoke mktexfmt and various font conversion tools. These will also cause pdflatex to print 'Transcript written on' lines for those steps. The existing regular expression does greedy matching, meaning that the full log output between the steps is parsed as the job name, causing latexrun to attempt to open non-existent files.
Author
|
Closing, as this is a duplicate of #47. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Whenever pdflatex is invoked on a clean copy of the texmf, it will first
invoke mktexfmt and various font conversion tools. These will also cause
pdflatex to print 'Transcript written on' lines for those steps.
The existing regular expression does greedy matching, meaning that the
full log output between the steps is parsed as the job name, causing
latexrun to attempt to open non-existent files.