b7197d9dc6
The GHC API changed a bit to accomodate the REPL changes since 7.2 (now most top-level decls can be used in the API.) Tested and working using virthualenv with GHC 7.0.4 and 7.2.1-rc1 |
||
---|---|---|
elisp | ||
.gitignore | ||
Browse.hs | ||
Cabal.hs | ||
CabalDev.hs | ||
Check.hs | ||
ErrMsg.hs | ||
ghc-mod.cabal | ||
GHCMod.hs | ||
Info.hs | ||
Lang.hs | ||
LICENSE | ||
Lint.hs | ||
List.hs | ||
README | ||
Setup.hs | ||
Types.hs |
Happy Haskell programming on Emacs Features: 1) Completions of keyword, module, class, function, types, language extensions, etc. 2) Flymake with GHC and hlint 3) Inserting code template The "ghc-mod" program written in Haskell is a backend to gather information from GHC and hlint. Elisp libraries including ghc-mod is an extension to haskell-mode. You should put the followings in your "~/.emacs.el": (autoload 'ghc-init "ghc" nil t) (add-hook 'haskell-mode-hook (lambda () (ghc-init))) or (add-hook 'haskell-mode-hook (lambda () (ghc-init) (flymake-mode))) Changes: If you have customized GHC import-path like follows, (setq ghc-flymake-check-includes '("dir1" "dir2")) You may update your settings as follows. (setq ghc-ghc-options '("-idir1" "-idir2")) or (setq ghc-ghc-options '("-idir1:dir2")) Now, you can simply pass GHC options to ghc-mod sub-commands. For more information, see: http://www.mew.org/~kazu/proj/ghc-mod/