In case there are fatal parse errors, using a token-based keyword highlighting mechanism could be useful, especially if a file was just opened and has no highlighting at all at that point.

Submitted by Lennart Kats on 24 April 2010 at 15:15

Alternatively, even a silly regex based highlighter can be a nice fallback, using the comment specification from the ESV and some default syntax for strings.

Better yet, we could collect all literals in productions in the parse table, and use those together with the default tokenization provided by the water recovery rules. Skipped regions would have to be tokenized separately.

Fixed in r20960. Currently doesn’t work for unrecoverable syntax errors (Spoofax/157).