Go to file
2014-08-01 17:08:50 +02:00
elisp fix #273. 2014-08-01 17:01:01 +09:00
Language/Haskell Merge remote-tracking branch 'kazu/master' 2014-08-01 17:08:50 +02:00
scripts Add script to collect debugging information. 2014-05-24 16:32:02 +02:00
src First attempt to add auto 2014-08-01 17:08:23 +02:00
test clean up lookupSymbol. 2014-07-18 15:13:30 +09:00
test-elisp adding test cases for elisp. 2014-04-23 14:51:02 +09:00
.ghci .ghci for ghci-friendliness (testing) 2012-01-22 20:16:22 -08:00
.gitignore Add add-source-timestamps to gitignore 2014-05-04 04:57:38 +02:00
.travis.yml Add workaround for #277 2014-07-04 19:03:57 +02:00
ChangeLog changelog. 2014-04-30 21:45:39 +09:00
ghc-mod.cabal First attempt to add auto 2014-08-01 17:08:23 +02:00
hcar-ghc-mod.tex hcar review. 2014-05-21 09:18:51 +09:00
LICENSE adding README and LICENSE. 2010-03-10 12:13:03 +09:00
README.md readme. 2014-05-19 16:42:34 +09:00
Setup.hs adding Setup.hs. 2010-04-03 00:16:22 +09:00

Happy Haskell Programming

Build Status

Please read: http://www.mew.org/~kazu/proj/ghc-mod/

Using the stable version

Emacs front-end, which is consistent with binaries on Hackage, is available stable MELPA whose URL is http://melpa-stable.milkbox.net/packages/. So, your "~/.emacs" should be:

(require 'package)
(add-to-list 'package-archives 
	     '("melpa" . "http://melpa-stable.milkbox.net/packages/"))
(package-initialize)

With this configuration you can install the stable Emacs front end indicated by "ghc" from MELPA while you can install ghc-mod/ghc-modi binaries by:

% cabal update
% cabal install ghc-mod

Using the develop version

You should install both Emacs front-end and binaries from this git repo. If you use the snapshot MELPA to install Emacs front-end, you would suffer from inconsistency between Emacs front-end and binaries.