-
Notifications
You must be signed in to change notification settings - Fork 27
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
Newlines on Windows #36
Comments
I am running into more subtle errors with newlines. The sympoms are paragraphs and even blocks not being detected correctly, leading to errors that are hard to trace back to the newlines. The most devious one I had was a block that took a After I switched the newline format in VSCode from CRLF to LF (you can do that by clicking on "CRLF" in the bottom right corner and choosing the other one), everything works as expected. This leads me to think that it might be possible and worth it to handle these different newline codes in elm-markup itself. |
I am having the same issue. I am having trouble compiling even basic markup syntaxes such as basic string parsing |
Yeah, I've just encountered the same issue when working with this. |
Not sure if this is an issue but I thought I would mention in case there is a way to prevent someone else having a similar issue?
I wanted to get a minimal example of Elm Markup working using reactor using Visual Studio Code ... but had an issue with the windows new-line characters being rejected as an error by Mark.compile.
The workaround was to use String.replace "\u{000D}\n" "\n"
I have included an copy of the error and the code example below.
The text was updated successfully, but these errors were encountered: