|  510ca3d3b6 * elisp/ghc.el * There are many ways to fix issue #351 so this is just one example and may not fit the style you prefer, so please feel free to use or not. It is easy to work-around the issue by setting ghc-initial-sig-key to another key combination before ghc-init, but it would be nice to have a fix. The use of C-u for this binding seems to be just as a flag, thus this change takes the simplest fix to achieve that purpose. | ||
|---|---|---|
| elisp | ||
| Language/Haskell | ||
| scripts | ||
| src | ||
| test | ||
| test-elisp | ||
| .ghci | ||
| .gitignore | ||
| .travis.yml | ||
| ChangeLog | ||
| 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
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.
