Does ecode show parsing errors with languages JSON files?

[groggily]

I'm talking about both the language.json and language.tmLanguage.json files.

My thought is instead of failing silently and doing no syntax highlighting at all (plain text), it's better to tell the users where it's stuck.

Not to talk about many poor quality syntax definitions that were converted to C++ submitted by various users.

Does ecode show parsing errors with them, too?

[SpartanJ]

Parsing as if JSON is invalid will be printed in the logs. It will display something like:

2025-05-29 00:39:51 - ERROR: SyntaxDefinition load failed:
[json.exception.parse_error.101] parse error at line 10, column 17: syntax error while parsing object - unexpected string literal; expected '}'

Which is the JSON parser error. Also ecode does lint JSON files natively, so it's also visible while editing.

My thought is instead of failing silently and doing no syntax highlighting at all (plain text), it's better to tell the users where it's stuck.

Parsing errors should be the least of the problems since they're obvious. The hard part is actually doing a correct highlighter.

Not to talk about many poor quality syntax definitions that were converted to C++ submitted by various users.
Does ecode show parsing errors with them, too?

Those obviously have valid code, otherwise ecode wouldn't compile. Highlighter quality is a different history. RegEx and Lua Patterns errors are also logged, but that doesn't mean anything, you can have a fully functioning grammar and everything can look completely wrong.