-
Notifications
You must be signed in to change notification settings - Fork 6.5k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
5 additions
and
7 deletions.
There are no files selected for viewing
This file contains 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
8246d0d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi, I think this broke
latex
rendering by indiscriminately invoking-no-pdf
8246d0d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My expectation is that in all cases one only needs the .dvi or .xdv file here, which is what's then converted to .svg, and you never need the pdf. When I run this on my system, both for latex and xelatex, it seems to work. Can you describe more about the issue you're seeing?
8246d0d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was setting up manimgl on Windows today for the first time and couldn't get the example scene running. It was throwing
manimlib.utils.tex_file_writing.LatexError: LaTeX compilation failed
which was a result of MiKTeX-pdfTeX 4.19 (called bylatex
env var) error. I could see the following in MiKTeX log:The "unknown option" turned out to be
-no-pdf
.xelatex
(MiKTeX-XeTeX 4.11), on the other hand, doesn't mind this option.MiKTeX-pdfTeX only produces .aux, .dvi, and .log for me when ran without
-no-pdf
.p.s. This is probably obvious to you but I had to make sure to clear the cache in order to properly test argument/option changes after a prior successful compilation.
Sorry, I probably should've opened an issue, but thought it was somehow an edge case on my setup. This commit seem like a plausible culprit tho.