Describe the bug

The generic "Parse error in" error which is always reported on line 1 and column 1 is confusing me. I want to look only at the real parse errors with the accurate locations.

I suspect this is produced by a downstream tree processor in the LSP server? We can/should assume that all parse errors have been reported by the parser process, or will be reported shortly asynchronously.