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
Infinite loop while Building #951
Comments
This looks to be an interesting malfunction by
|
Debugging some more, the current master claims that:
So there may also be a schema tweak needed. I will focus on ensuring schema mismatches don't lead to infinite loops in general until @brucemiller imparts schematic wisdom here, as a general case guard. |
Problem with naming What's bizarre is that it would need to open |
Ah! That naming distinction "threw me in for a loop". So I think I can add a guard that terminates early when a new auto-open attempts a name that has already been auto-closed (during a |
Probably just need more threads... Not clear what's happening ( |
Adding new thread where we can discuss the generic guard - now implemented at #952 Onto the specific framebox schema mystery in this issue. I can confirm your observations. I wish I understood the |
Also, it feels like we should add a schema-oriented test, using this |
Actually was a bit fishier: |
Sweet! |
Deyan from the future here. I've started wondering whether we shouldn't define And here is the reason I am recording this thought: \newcommand{\qed}{{ \hfill
{\unskip\kern 6pt\penalty 500
\raise -2pt\hbox{\vrule\vbox to 6pt{\hrule width 6pt
\vfill\hrule}\vrule} \par} }} latexml doesn't really draw this right, but of course - even if it did - the resulting HTML is horrifying to inspect by humans, just as the original TeX is. So, alternatively, maybe we should get enough upgrades in to draw the box correctly? :> Just a thought for now. |
I have extracted a minimal example from the infinite loop reported at arxiv-vanity/engrafo#280
which converted 1404.2371 from arXiv. The minimal example is:
which produces the log:
and keeps Building ad infinitum.
The framebox argument should be playing a major role here. pdflatex succeeds and creates the expected:

I am hunting for two separate fixes here:
The text was updated successfully, but these errors were encountered: