You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using VS Code and GHC 9.2.8, a spurious error is shown for line 1 of docs/inthelarge.lhs:
\documentclass{article}
> unlit' failed in phase Literate pre-processor'. (Exit code: 1) compiler
I don't know the cause, but a workaround is to insert at the top of the file: \begin{code} \end{code}
which eliminates the error message.
The text was updated successfully, but these errors were encountered:
I wonder if it's because that file contains zero actual Haskell code. It's actually a bit silly for it to be a .lhs file, it ought to just be a .tex file. Perhaps I made it an .lhs file since then I could process it with the exact same pipeline as all the other files. But I really don't remember.
I think the file is still syntactically correct .lhs. My hunch is that unlit.c is the problem. There was a recent patch to unlit.c, but it still is rejecting a proper TeX code. I was tempted to go down that rabbit hole, but I found the workaround instead, fortunately!HowardOn Aug 1, 2023, at 12:48 PM, Brent Yorgey ***@***.***> wrote:
I wonder if it's because that file contains zero actual Haskell code. It's actually a bit silly for it to be a .lhs file, it ought to just be a .tex file. Perhaps I made it an .lhs file since then I could process it with the exact same pipeline as all the other files. But I really don't remember.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
Using VS Code and GHC 9.2.8, a spurious error is shown for line 1 of docs/inthelarge.lhs:
\documentclass{article}
>
unlit' failed in phase
Literate pre-processor'. (Exit code: 1) compilerI don't know the cause, but a workaround is to insert at the top of the file:
\begin{code} \end{code}
which eliminates the error message.
The text was updated successfully, but these errors were encountered: