1. 22
  1.  

  2. 3

    I don’t know how to write Hakell (yet) but I’m impressed and scared of that walk through all at the same time.

    1. 3

      About a third of this is generally useful vim config/plugins. In the Haskell-specific the ghc-mod stuff (type annotations, inline errors) is super valuable, the rest is nice-to-haves for autocompletion.

    2. 2

      Sigh. I never managed to get a setup like that to work.

      1. 1

        I had a good setup going with ghc-mod, neco-ghc, youcompleteme and vim-plug. Minimal configuration too. I’ve since switched to spacemacs for various reasons, but someday I’ll try to set it up in neovim, see how that goes.

        1. 1

          I find Atom very good for Haskell work, due to the great Haskell autocomplete plugins available for it. I tried it with vim and neocomplcache, but the fact that autocomplete plugins block the main thread in vim made it somewhat unusable.

          1. 1

            Well the someday ended up being today (Trying out musl void linux and there was no emacs package). It has async plugin support so I’ve installed deoplete and neo-make, I’ll try it out on some c code later on (Going through k&r). But since neomake can call compilers asynchronously, the long waits should be gone.

            I’ve never been a huge fan of Atom, I tried it out a few times, but it always seemed a little slow.

            1. 1

              I’ve only been using Atom for a few weeks now, I haven’t found it slow yet (though I did when I first tried it a year ago). I have also just upgraded to new hardware though, so maybe that has something to do with it not seeming slow. We’ll see.