From 6f9fbc6e02a55d0e0ad24dc6384240c8950f9fc4 Mon Sep 17 00:00:00 2001 From: Kazu Yamamoto Date: Mon, 19 May 2014 16:25:38 +0900 Subject: [PATCH] readme. --- README.md | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index fe332d9..46d084c 100644 --- a/README.md +++ b/README.md @@ -3,4 +3,18 @@ Please read: [http://www.mew.org/~kazu/proj/ghc-mod/](http://www.mew.org/~kazu/proj/ghc-mod/) -Latest ELisp front-end can also be installed via [MELPA](http://melpa.milkbox.net/). The package name is "ghc". But it appeared that if you use MELPA, inconsistency between Emacs front-end and ghc-mod/ghc-modi happens. So, please use github directly. +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: + +```elisp +(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: + +```shell +% cabal update +% cabal install ghc-mod +```