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
iex(1)>Lua.parse_chunk("asdf"){:error,["\e[31m\e[1mParse Error\e[0m\n\n at line 1, column 1:\n\n A bare variable reference isn't a Lua statement.\n\n\n\e[31m 1 │ asdf\e[0m\n\e[31m^\e[0m\n\n\e[36mSuggestion:\e[0m\n To call it as a function, add parentheses: 'name(...)'. To assign to it, write 'name = value'."]}
Claude says
"Lua.parse_chunk/1 returns ANSI-colored strings in its {:error, reasons} tuple; Lua.Parser.Error.format/2 bypasses the #304 TTY gating"
Additionally i woud be i favour to get structured errors instead of a string like {:error, %Lua.CompilerException{}}. We could still get a string representation with Exception.message/1
Activity
kevinschweikert commentedon Jul 8, 2026
Additionally i woud be i favour to get structured errors instead of a string like
{:error, %Lua.CompilerException{}}. We could still get a string representation withException.message/1kevinschweikert commentedon Jul 13, 2026
Should be closed by #383 AFAIk