-
Notifications
You must be signed in to change notification settings - Fork 82
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
java.lang.IllegalArgumentException: Unknown ansi-escape [2m at index 262 inside string cannot be parsed into an fansi.Str #730
Comments
Thanks for reporting looks like a bug within https://github.com/com-lihaoyi/PPrint though I can't see anything in your code that would cause it. You can use the to-string modifier which will avoid using pprint. You should also see what is pprint choking on. |
@tgodzik |
Ach, that's right, it seems the issue is that the Console reported is trying to color the issue RED and it's failing to do so. Would be great to figure out what is the error that is causing it and report it upstream to fansi. We should also make sure that we can revert to toString for Console reported if fansi has issues. Maybe even fansi is not needed there 🤔 |
What error do you get when compiling the snippet normally? |
Are you able to copy that in text form? We could try to isolate exactly what is breaking. |
Yes I can:
|
Looks like the issue is com-lihaoyi/fansi#46 we should be able to apply the same workaround |
Previously, some error messages might have been not able to be printed due to a bug in fansi com-lihaoyi/fansi#46 Now, we added a workaround that should help out here. Fixes scalameta#730
Previously, some error messages might have been not able to be printed due to a bug in fansi com-lihaoyi/fansi#46 Now, we added a workaround that should help out here. Fixes #730
Main.scala
docs/index.md:
build.sbt
Produced errors:
Does anyone have any clues why mdoc cannot compile my markdown file?
The text was updated successfully, but these errors were encountered: