> nix-shell -A env
my fault - sry.
In the past I used sourceAndTags to get sources tagged (using hasktags)
so that I was able to jump to source using Vim's :tjump command (and
search names) fast.
Is this workflow "outdated" eg because hoogle can do it or should I try
integrating it into
I think you might want to use:
nix-shell -A env
The `env` attribute creates a derivation that brings in GHC. You can
generate a shell.nix via `cabal2nix --shell` which detects if you're
in a shell and automatically uses the attribute.
On 23 June 2016 at 19:24, Marc Weber
It's way too much work to keep maintaining my nixpkgs-haskell-overlay.
Trying the workflow specified in the manual:
1) ./default.nix:
{ nixpkgs ? import {}, compiler ? "ghc7102" }:
nixpkgs.pkgs.haskell.packages.${compiler}.callPackage ./foo.nix { }
2) cabal2nix . >| foo.nix
3) nix-shell
