Add Haskell Makers about neomake HOT 7 CLOSED

Wrt the extra lines, see #27. About the parts of the message that are missing, I'm guessing the errorformat is somehow wrong. When I have ported makers from syntastic and it doesn't work right, usually there is some subtle difference between the errorformats. Unfortunately I'm no expert on vim's errorformat system, so I can't see the issue right off the bat. I can't look at it right away, but if you don't have any luck with it I'd be happy to try my hand at it sometime soon.

from neomake.

I actually think this has to do with #15. When I ran each linter in isolation, it worked perfectly. Do you get the same results every time? It's possible that some multiline messages are getting split up between two different job activity handler calls. Try putting let g:neomake_serialize = 1 somewhere in your ~/.vimrc and let me know if that fixes it.

from neomake.

Hmm, when I enable neomake_serialize I don't receive any hints from ghcmod at all(although I do get Neomake: ghcmod complete).

When I change haskell_enabled_makers to only ghcmod, I get the same erroneous output as above(without the HLint feeback).

from neomake.

Ok, I would make sure your version of neovim is relatively recent. I've been building weekly from master and testing agains that. Sometime this weekend I'll see if I can't get this going for myself and track down the different issues here.

from neomake.

Still happening off of nightly.

It seems specific to the top-level binding warning, I don't see it happening with others during my normal use.

Let me know if you need help getting set up. Usually you can just install cabal-install via your package manager, then run:
cabal update && cabal install hlint ghc-mod && export PATH=~/.cabal/bin/:$PATH.

from neomake.

It looks like I was able to figure this out. When running this linters in normal vim, I saw it was outputting ^A at each place that was breaking in neovim. So I did some digging with ghc-mod check test.hs | hexdump and saw that ghc-mod is outputting a null byte at each location that breaks. Neovim breaks in a different way from vim; it interprets null bytes in stdout from jobs as newlines it seems. This has come up as a problem with ghc-mod before.

I was able to fix it with a small output formatting step. I included both these makers in the repo as well.

from neomake.

Beautiful, thanks :)

from neomake.