Closed raddessi closed 3 years ago
You shouldn’t run alex’ default (markdown), on non-markdown files. You can pass --text
to read input as text.
FWIW, when going through the next wave of dependency updates, this error will be gone!
Gotcha! I'll update to the and see what changes. Thanks
Ahh that totally fixes it. OK, I get what is going on. From my first read of the docs I had assumed that alex was doing a file identification automatically and that the --text
etc flags were to override that automatic identification only. Thanks for the advice! It works as expected on scripts now :)
Subject of the issue
When running over a file with the contents:
Alex gives an error in a nonstandard format:
I have tried to track down the cause of this but have not had any luck in a quick search.
Your environment
Steps to reproduce
Working example info is above.
Expected behaviour
Either an error should be raised in the normal format so it can be fixed or ignored, or the ampersand should just not cause issues?
Actual behaviour
It seems like something fails when reading the ampersand character.