[Haskell-cafe] [ANN] sarsi - A universal quickfix toolkit and his protocol (nvim/vim)

Alois Cochard alois.cochard at gmail.com
Sat Apr 16 15:57:57 UTC 2016

Hi Daniel,

I thought that the motivation part in the blog post would answer that,
seems like it's not enough.

You see, when you use ghc-mod or other similar integration of the like, it
usually type check the code in your active project, but such tools doesn't
have a complete vision of your project (like source dependencies as
mentioned in the blog post). Due to that, the error reported in ghc-mod/...
might be different (and sometime not so useful) than the one returned by
the build tool. I mean I always want to fix the first error reported by my
build tool, not an other one in the file I'm viewing, etc ...

The motivation was to be able to populate the quickfix list using the
output of the build tool (which is usually run continuously on file change,
there is an example using `entr` in the README), as an alternative to using
mainly the type checker. I see both as useful, but in different context.

If you never felt frustrated with your current setup, you probably won't
see much benefit in this approach, but personally, I am much more
productive using the one *sarsi* offer.


On 16 April 2016 at 15:49, Daniel Trstenjak <daniel.trstenjak at gmail.com>

> Hi Alois,
> I think that I know vim and the Haskell development environment quite
> well, but have a hard time to get what sarsi really is.
> It seems to be something about running a compiler (continuously?)
> and saving the error messages per file?
> In the documentation a motivation might be missing like e.g. what it
> does beyond - or better than - the vim integrations of ghc-mod oder
> hdevtools?
> Greetings,
> Daniel
> _______________________________________________
> Haskell-Cafe mailing list
> Haskell-Cafe at haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/haskell-cafe/attachments/20160416/4f2146b7/attachment.html>

More information about the Haskell-Cafe mailing list