As suggested by Bjorn I am sending the following bug report to this
group.  I have reached out to the plugin maintainer mentioned in the
head of the file, but I did not yet receive a response.  I have worked
around the issue for the moment, but It may affect others and was a
bit tricky (as a relative newcomer to vim/macvim) to track down. The
root cause seems to be improper args passed to the ruby 'ri' command
which is what populates the balloon.

The bug report with all the details:
http://code.google.com/p/macvim/issues/detail?id=342

Summary of the issue:

What steps will reproduce the problem?

Mouse over a method name in Ruby code that triggers the ballooneval
tooltip to display.

What is the expected output? What do you see instead?

Should show ruby ri output for the method name.  Instead it shows a
usage message for ri because ri is being called with an invalid set of
options.

See the following line of code:
https://github.com/b4winckler/macvim/blob/master/runtime/ftplugin/ruby.vim#L194

the argument '-f simple' is invalid for ri and the balloon is showing
the entire 83 line usage message for ri instead.

>From the usage message:
...
-f, --format=NAME                Uses the selected formatter. The
default
                                     formatter is bs for paged output
and ansi
                                     otherwise. Valid formatters are:
                                     ansi bs html rdoc

...
"invalid argument: -f simple"

What version of MacVim and OS X are you using (see "MacVim->About
MacVim"
and  "Apple Menu->About This Mac" menu items, e.g. "Snapshot 40,
10.5.6
Intel")?

Snapshot 59 installed from homebrew, OS X Intel 10.7 Lion GM

Please provide any additional information below.

After tracking down the root cause of this (which took a while) I
tried to disable this functionality in my .gvimrc file.  I could get
the balloon to stop displaying in macvim if I issued ':set
noballooneval' in my vim window.  However, putting the same command in
my .gvimrc file failed to do anything that I could notice.  I worked
around this by adding 'set balloondelay=100000' in that file.  This
seems to do the trick.

-- 
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

Raspunde prin e-mail lui