Skip to content
Happy Haskell Hacking for editors
Haskell Emacs Lisp Shell Other
Failed to load latest commit information.
Data/Binary Fix ghc-7.4 build
Language/Haskell Merge release- into master (using imerge)
NotCPP Bring test suite up to date
System/Directory NFData fix for ClockTime on GHC 7.4
doc Update MELPA URL
elisp Bump version to
hackage-metadata Update metadata
scripts skip bump commit when empty
src Merge branch 'fix-718' of int…
test-elisp adding test cases for elisp.
test Make runGhcModT thread lock test more reliable
.ghci .ghci for ghci-friendliness (testing)
.gitignore Add Stack build configuration
.travis.yml Fix travis
COPYING.AGPL3 Change primary license to AGPL-3
COPYING.BSD3 Change primary license to AGPL-3
CodingStyle adding CodingStyle.
LICENSE Add back LICENSE file pointing to COPYING.* README: Use master branch for travis-ci status image
Setup.hs Remove dependency on Safe from Setup.hs
SetupCompat.hs SetupCompat.hs: remove dependnece on mtl
Utils.hs Fix upper bounds on binary for ghc<7.10
ghc-mod.cabal Merge release- into master (using imerge)
ghcmodHappyHaskellProgram-Dg.tex Update HCAR entry
stack.yaml Update stack.yaml

Happy Haskell Programming

Build Status

Please read:

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" . ""))

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

ghc-mod works fine for users of Nix who follow a recent version of the package database such as the nixos-15.09 or nixos-unstable channel. Just include the package ghc-mod into your ghcWithPackages environment like any other library. The Nixpkgs Haskell User's Guide covers this subject in great detail.

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.

Custom ghc-mod cradle

To customize the package databases used by ghc-mod, put a file called ghc-mod.package-db-stack beside the .cabal file with the following syntax:

temp directory root
package db 1
package db n

each package database line is either a path to a package database, or global or user.


If you have any problems, suggestions, comments swing by #ghc-mod (web client) on Freenode. If you're reporting a bug please also create an issue here so we have a way to contact you if you don't have time to stay.

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. You're most likely to get an answer during the day in GMT+1.

Something went wrong with that request. Please try again.