id,summary,reporter,owner,description,type,status,priority,milestone,component,version,resolution,keywords,cc
14,let user decide whether balloneval should be set,phercek,haskellmode,"The bigger a project is the more annoying {{{ballooneval}}} is. The problem is that such an innocent thing as moving a mouse to an edit location can result in a background load to ghci to find out the type information which freezes vim GUI for a potentially long period. User is left wondering why vim stopped to respond. An easy workaround is to switch off {{{ballooneval}}} but this works well only when it is not set on again during {{{:make}}}. Do not set {{{ballooneval}}} in ghc.vim. Let user decide whether he/she wants it on. He/she can do it in {{{~/.vimrc}}}. A more complicated option would be to provide something like {{{g:haskellmode_beval}}} to control whether vim haskellmode can set {{{ballooneval}}} on.
Here is the simpler solution:
{{{
--- ghc.vim.old	2009-09-16 16:18:39.000000000 +0200
+++ ghc.vim	2009-09-16 16:31:18.000000000 +0200
@@ -112,7 +112,6 @@
 
 "" show type of identifier under mouse pointer in balloon
 if has(""balloon_eval"")
-  set ballooneval
   set balloondelay=600
   set balloonexpr=GHC_TypeBalloon()
   function! GHC_TypeBalloon()
}}}",defect,closed,major,,---,,fixed,,