We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi, I believe this is a bug in lhs2Tex-hl. When there is an underscore in a constructor declaration, e.g.:
data FOO = Bar_A | Bar_B
the formatting generated is
%format Bar_A = " {\lhsCHconstructor{Bar_{A}}}"
which causes LaTeX to choke, as the underscore is not in a math environment. Maybe outputting an escaped underscore
%format Bar_A = " {\lhsCHconstructor{Bar\_{A}}}"
or formatting the whole thing as a subscript
%format Bar_A = " {\lhsCHconstructor{Bar$_{A}$}}"
would be possible solutions.
Br, Martin
The text was updated successfully, but these errors were encountered:
Btw, uncommenting line 14 in Language/LaTeX.hs seems to make it work, though I haven't been able to test whether it breaks something else.
. replace "_" "\\_"
Sorry, something went wrong.
The idea is that the system takes care of some formatting for you when you insert a _. Apparently that is broken now, I will look into it.
_
Ok, I had understood that from the documentation as well.
No branches or pull requests
Hi, I believe this is a bug in lhs2Tex-hl.
When there is an underscore in a constructor declaration, e.g.:
data FOO = Bar_A | Bar_B
the formatting generated is
%format Bar_A = " {\lhsCHconstructor{Bar_{A}}}"
which causes LaTeX to choke, as the underscore is not in a math environment.
Maybe outputting an escaped underscore
%format Bar_A = " {\lhsCHconstructor{Bar\_{A}}}"
or formatting the whole thing as a subscript
%format Bar_A = " {\lhsCHconstructor{Bar$_{A}$}}"
would be possible solutions.
Br,
Martin
The text was updated successfully, but these errors were encountered: