Daniel Hahler

> It would be nice if any errors that were attributed to nonexistent line numbers were associated with the last line of the program. Makes sense. Except for `< 1`,...

Yes, thanks. > 11:49:30 2046 [D +0.07] [2.2:1:1] output on stderr: ['# github.com/sbromberger/vt1', '../../src/github.com/sbromberger/vt1/main.go:13:1: syntax error: unexpected EOF, expecting }', ''].

You can try to call `:call neomake#virtualtext#show_errors()` manually. I've thought for it to be less distracting to only display the current error.

Cool. It could be done by changing `neomake#virtualtext#displayhandle_current_error` to display all errors then maybe. But it seems not trivial to refactor / change this. And I'd rather use popup /...

> UPD: it's probably not because of message type, but because clangcheck entry doesn't contain bufnr. Yeah. Check the output of `:echo getloclist(0)` to see where the entries differ -...

Thanks for the report. There is https://github.com/neomake/neomake/pull/1788, which would allow to use a custom dir (and the original filename), but that would not work with imports etc then. The best...

Awesome. Appears to not be released yet, but I'd be happy to review a PR for it already.

I assume you mean the cmdline, or buffer highlights? (Neovim) The former are being truncated currently, but could probably be made wrapping if `cmdheight` is more than 1 (patch would...

Sure, please create a PR. From the description it looks like it could be preferred automatically (based on `executable('revive')` then also over golint? https://github.com/neomake/neomake/blob/ba38b8786ce68c36fc3cd2139a7820b25bea378a/autoload/neomake/makers/ft/go.vim#L10

Also example output, and a test would be nice to have then here or with the PR.