Skip to content
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

Download as latex has (non-critical) compile errors #34

Open
ivanistheone opened this issue May 24, 2021 · 1 comment
Open

Download as latex has (non-critical) compile errors #34

ivanistheone opened this issue May 24, 2021 · 1 comment

Comments

@ivanistheone
Copy link

I downloaded a very simple Article (contains a single block of text, no images, no interactive, or anything fancy), see v1.AelWbQuHSmO3VWhgAZk2Gk6XWQ52.latex.zip

Then on compiling on Mac with pdfTeX 3.14159265-2.6-1.40.19 (TeX Live 2018), I saw the following errors:

Screen Shot 2021-05-24 at 1 40 56 PM

Screen Shot 2021-05-24 at 1 41 21 PM

Screen Shot 2021-05-24 at 1 42 32 PM

pressing ENTER through them and the document compiled in the end, but most people might freak out about these errors and not know how to continue, so I'd recommend fixing them (and testing with MikTeX which is the commonly used TeX distribution by windowls people).

pro-tip: if you want to ignore all non-critical errors and make LaTeX very tolerant, you can add this to the document preamble and it will do it's best to compile the document even if it encounters errors:

\scrollmode
\nonstopmode

(generally not good move, since you will not get warnings/errors right away when you add errors, but good hack to avoid people filing issues ;)

@stevejpurves
Copy link
Member

thanks for reporting this @ivanistheone.

I'm running with nonstopmode on via the command line while using xelatex for the build itself in testing, but adding that to the preamble would stop people's builds being interrupted at least 👍

Errors 1 & 2 look immediately solvable. The third issue is related to the minted package for code highlighting which we're including even though we don't have code included in your example. I think we can look at content based adding of packages so that it's only included when there are code blocks but some better info output advising of the dependency when there is code is probably needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants