Matthieu Coudron

I have a similar question, the LSP client shows `Mismatching GHC versions: Project is 8.6.4, HIE is 8.6.3` with this shell.nix: ``` with import {}; let hie_remote = builtins.fetchTarball {...

I had a look at the code so one can pass its own compiler: `hie = (import hie_remote { compiler = pkgs.haskell.compiler.ghc864; } ).hie86;` and lose the cache or alternatively...

So I might have been carried away since niether works. If I try `haskell.packages.ghc863.shellFor {` then I get ``` runghc daemon.hs Loaded package environment from /home/teto/mptcpnetlink/hs/.ghc.environment.x86_64-linux-8.6.3 : cannot satisfy -package-id...

@jhenahan aaaahhh~~~ that did it thanks

if you dont use channels, that may be why. I modified NIX_PATH to point at a local checkout `export NIX_PATH=nixpkgs=.` and then manix could find results, but still with errors...

I've opened https://github.com/nix-community/docker-nixpkgs/pull/29 . Should I prepend ~/.nix-profile/bin in PATH in this MR or another ? It's a bother to add when installing stuff via nix-env

sure for the hlint changes, gonna drop. Now I wonder about how to enable a more verbose hie-bios: should I: 1/ just disable the automatic `verbisotiy0` to let a cradle's...

I would very much like this. I am currently porting my application from python to haskell and I dearly miss the integrated test generation ("transcript") of https://github.com/python-cmd2/cmd2 where you can...

I would like to rewrite one of my program from python to haskell. It would be nice to have the same level of autocompletion as https://github.com/python-cmd2/cmd2. I make extensive use...

> BTW, a more direct way to refer to the default devshell in shell.nix would be using .shellNix.default instead of just .shellNix; omitting the .default part results in Nix scanning...