45d6b7d67a
If cabal.sandbox.config contains a "package-db:" declaration with the wrong path and only the ghc version is wrong, for example: ``` package-db: <DIR>/.cabal-sandbox/x86_64-linux-ghc-7.8.3-packages.conf.d ``` Even though the user is using 7.10.0.20141222 `cabal repl` will correct this and pass ``` -package-db <DIR>/.cabal-sandbox/x86_64-linux-ghc-7.10.0.20141222-packages.conf.d ``` to ghci, so obviously Cabal/cabal-install is doing some magic. Conflicts: Language/Haskell/GhcMod/PathsAndFiles.hs |
||
---|---|---|
doc | ||
elisp | ||
Language/Haskell | ||
scripts | ||
src | ||
test | ||
test-elisp | ||
.ghci | ||
.gitignore | ||
.travis.yml | ||
CodingStyle | ||
ghc-mod.cabal | ||
hcar-ghc-mod.tex | ||
LICENSE | ||
README.md | ||
Setup.hs |
Happy Haskell Programming
Please read: http://www.mew.org/~kazu/proj/ghc-mod/
Using the stable version
The Emacs front-end is available from stable MELPA. This package should always be compatible with the latest version of ghc-mod from hackage.
To use stable stable MELPA add this to your .emacs
:
(require 'package)
(add-to-list 'package-archives
'("melpa" . "http://melpa-stable.milkbox.net/packages/"))
(package-initialize)
With this configuration you can install the Emacs front end from MELPA (the
package is called ghc
there, not ghc-mod
) and install the
ghc-mod
/ghc-modi
binaries from hackage by doing:
% cabal update && cabal install ghc-mod
Nix & NixOS
The installation is a little more involved in this environment as Nix needs some ugly hacks to get packages using the GHC API to work, please refer to this stackoverflow answer:
http://stackoverflow.com/a/24228830
Using the development version
The easiest way to hack on ghc-mod is compile it, then add dist/build/ghc-mod
and dist/build/ghc-modi
to your PATH
and add the elisp/
directory to your
Emacs load-path
.
Make sure you're not using the MELPA version of ghc.el
otherwise you might get
all sorts of nasty conflicts.
IRC
If you have any problems, suggestions, comments swing by #ghc-mod on Freenode.