-
Notifications
You must be signed in to change notification settings - Fork 36
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
Fix long file names #62
Conversation
This surprisingly makes Edit: after a bit of fiddling, 480 seems to be working fine and is hopefully long enough. |
d9b9b05
to
c614b54
Compare
Looks like 480, despite working >10 times locally, is still not working 100% of the time for this test. Not sure what's wrong... |
I actually just got the same issue with 80, so this is unlikely to be related - looks like there's an issue with this test. |
latexrun doesn't properly parse LaTeX's output when the filename doesn't fit in a single line - see aclements/latexrun#19. This forces it to use 480 as a max line length, effectively working around this issue. Fixes ProdriveTechnologies#50
c614b54
to
702b957
Compare
@patbro Did you observe any issues with |
I don't recall any issues with that package to be honest. But maybe my memory fills in the blanks here as well... Maybe this is a Cirrus CI thing? Which might be solved when switching. |
This should probably be fixed by applying aclements/latexrun#52 instead. |
Closing in favour of #98 |
latexrun doesn't properly parse LaTeX's output when the filename doesn't fit in a single line - see aclements/latexrun#19. This forces it to use
480 as a max line length, anything significantly longer seems to break something withMAX_INT
as a max line length, effectively leaving the line-wrapping job up to the terminal (which should be its responsibility, not LaTeX's), and works around this issue.//packages:glossaries-extra
Fixes #50