Forcing DVI output#320
Merged
Merged
Conversation
M-Lampert
approved these changes
Jul 9, 2026
M-Lampert
left a comment
M-Lampert
left a comment
Contributor
There was a problem hiding this comment.
Looks good. Feel free to merge.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Local testing was failing for me because one of the commands is assuming a
dvioutput (which a later step consumes) without specifying its flag explicitly. This seems to be working on the CI but was failing in my case - the code assumes latexmk's default target is DVI, but my locallatexmkdefaults to PDF.This tweak should fix it for the general case.