Type check errors in quickfix window

[mlopes]

When running :EnTypeCheck, it highlights the errors and then shows them when passing with the cursor over the code causing the error. This error is being shown in the command area, which means we get a message "Press ENTER or type command to continue" unless we set command height to at least 4 (the size of the output of a EnTypeCheck error).
I'm wondering if using vim's quickfix window could be a better option, allowing the user to quickly navigate through typecheck errors and not get stuck on the error line every time they pass over it?

[ches]

Hi Marco, ensime-vim has built-in Syntastic integration support that essentially provides quickfix lists for this—I think most users use this, or perhaps wire up integrations with alternatives like Unite. That said though, I’d be glad to consider PRs for improving how this works out-of-the-box with no other third-party plugin (or shipping integrations in addition to Syntastic with ensime-vim). I believe we might have another enhancement ticket along these lines already, I’m on the go at the moment so I haven’t searched.

…

[mlopes]

I’m using ale for syntax checking. Not sure if there will be an easy way to integrate. I’ll have to look into what are my options.

Thanks for your reply.

[mlopes]

Ok, I might have a go at making this work. It seems like a checker can be added to ale's registry:

ale#fix#registry#Add(name, func, filetypes, desc) *ale#fix#registry#Add()*

Now this is where I get a bit confused. In ensime-vim, a checker is registered with syntastic:

ensime-vim/syntax_checkers/scala/ensime.vim

Line 28 in dbf5976

call g:SyntasticRegistry.CreateAndRegisterChecker({

but it sets 'exec': '/bin/true and I can't really see how syntastic gets the data from ensime-vim when for example a type check fails.

[GordianDziwis]

I am trying to integrate ensime with neomake. Neomake does support callback function for a maker, but I do not know which function to call. Any hint?
I looks like the syntastic integration gets it data from b:ensime_notes which exists but is always empty.

Update: Found a workaround/hack

[MaxWorgan]

@mlopes did you get anywhere with this - I'm trying to achieve the same thing.

[mlopes]

Hi,

No, I know very little about vim plugin development, never really got to the bottom of how this integrates with syntastic. It doesn’t look like it should be to hard though.

[mlopes]

This seems to make things really hard to use. When there's an error, putting the cursor over the error repeatedly asks to press enter making it really hard to fix the bug because it prevents typing anything else. The workaround is to set the loclist size to something like 5 rows, either temporarily when the error occurs or permanently and lose 5 rows of screen real estate.

Also, in the description I've said quickfix window but meanwhile I found that this is using the loclist.

[santiagodoldan]

Anyone was able to integrate this with ale or neomake?

[tdgs]

bump

[mlopes]

#415

This PR fixed this issue