-
Notifications
You must be signed in to change notification settings - Fork 28
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
Improve error messages in ulex parsing #2
Comments
petekeller2
added a commit
to petekeller2/APE
that referenced
this issue
Sep 8, 2018
This partially addresses issue Attempto#2. Malformed file errors will display the line number of the line that is causing the error.
Kaljurand
pushed a commit
that referenced
this issue
Sep 9, 2018
This partially addresses issue #2. Malformed file errors will display the line number of the line that is causing the error.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When loading the user lexicon, e.g. by
then some syntactically incorrect lexicon entries, e.g.
currently result in uninformative error messages, e.g.
The text was updated successfully, but these errors were encountered: