LCD 047

There are two ways to do this: (1) toggle various bits of what is displayed, and make the change take effect immediately on what is shown to the user, without...

Vim's loclists don't support multiline messages.

Sadly, there are good reasons for removing newlines from error messages, and syntastic implicitly assumes that. Vim replaces newlines on input with ASCII `NUL`s, and various functions are not prepared...

Aside from the issues pointed out by @sharkdp, `errorformat` is wrong. Without looking at what this is supposed to match, the following fixes the syntax errors: ``` vim let errorformat...

> There's no way to display multiple lines in syntastic errors that I am aware of. @lcd047 is that correct? It depends on what you mean by that. Loclist windows...

@paf31 As far as I'm concerned building the project while checking is annoying, but not fatal. Other checkers do that, and people still use them. The real show stopper however...

@paf31 Something like `/path/to/file:6.3-6.7: Expression 33 does not have type Prim.String` would be perfect. JSON would be fine too, and probably more flexible. One more thing: column numbers should be...

@seanhess The current code has various problems, and the changes kindly offered by @paf31 would make a big difference. If you need a checker right now, perhaps you can maintain...

@seanhess Sadly, useful to you != problem-free for me. Missing errors is a great source of bug reports, and a legitimate one at that. _shrug_

I looked at Pyre, and I'm not optimistic about being able to write a working syntastic checker for it. First, it's isn't clear to me how this is supposed to...