Restore the original meaning of g:ghcmod_use_basedir (#25)

The default directory to execute ghc-mod from has changed.

Author: eagletmt

autoload/ghcmod.vim

@@ -457,10 +457,10 @@ endfunction"}}}
 
 function! ghcmod#basedir()"{{{
   let l:use_basedir = get(g:, 'ghcmod_use_basedir', '')
-  if !empty(l:use_basedir) && l:use_basedir ==? 'yes'
+  if empty(l:use_basedir)
     return s:find_basedir()
   else
-    return expand('%:p:h')
+    return l:use_basedir
   endif
 endfunction"}}}
 

doc/ghcmod.txt

@@ -137,14 +137,13 @@ g:ghcmod_type_highlight                              *g:ghcmod_type_highlight*
 	let g:ghcmod_type_highlight = 'ghcmodType'
 <
 g:ghcmod_use_basedir                                    *g:ghcmod_use_basedir*
-	When value is 'yes' ghc-mod is executed from project base directory,
+	The directory to execute ghc-mod from.
+
+	If you do not set it, ghc-mod is executed from project base directory,
 	e.g. from directory where cabal file is placed. This can have an
 	effect particularly on template Haskell splices that expect to find
 	certain files in certain places.
 
-	If you do not set it, ghcmod will be executed from the folder the file
-	current Haskell file is contained in.
-
 g:ghcmod_max_preview_size                          *g:ghcmod_max_preview_size*
 	The maximum size in lines of that the preview window will grow to
 	while under the control of ghcmod. Useful for preventing huge lists