Open nsensfel opened 4 years ago
This should now be working properly.
It has improved, but there are still cases where the location of the issue isn't pointed out in any other detail than the file in which it occurred. This isn't enough.
Example of case where the reported error doesn't help enough: writing (cond 42)
.
Still an issue in 050e329f2a2e2367c2e4f1965190b0f6a5addf29. When the parser invalidates the input or when there is a Java error, it is still rather hard to figure out exactly what part of the narrative is causing the issue.
Issues in parsing raised by ANTLR indicate messages looking like the following:
At no point is the file containing these lines indicated, making it difficult to locate the issue.