744f2c232c
|
||
|---|---|---|
| Language/Haskell | ||
| NotCPP | ||
| doc | ||
| elisp | ||
| scripts | ||
| src | ||
| test | ||
| test-elisp | ||
| .ghci | ||
| .gitignore | ||
| .travis.yml | ||
| COPYING.AGPL3 | ||
| COPYING.BSD3 | ||
| CodingStyle | ||
| LICENSE | ||
| README.md | ||
| Setup.hs | ||
| SetupCompat.hs | ||
| Utils.hs | ||
| ghc-mod.cabal | ||
| hcar-ghc-mod.tex | ||
README.md
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.
Do hang around for a while if no one answers and repeat your question if you still haven't gotten any answer after a day or so.