Benjamin R. Haskell wrote:
On Wed, 21 Sep 2011, Sergey Khorev wrote:
was also posted here [2] but that post never got any
attention so I am bringing it up once again.
The plugin author is apparently not responding to emails.
[1] http://code.google.com/p/macvim/issues/detail?id=342
[2] https://groups.google.com/forum/#!topic/vim_dev/2lEb8Dt6ttc
[3] http://icy.io/misc/latest-macvim-ruby-annoying-ri-balloon-issue/
[4]
https://github.com/EricR/macvim/commit/051330cddd348c6ff323568d96fd691dbfcacd8f
Ok, so subject line is misleading: actual problem is not with balloon
eval at all but with Ruby ftplugin. If the plugin author does not
reply to emails I guess it is now up to Bram to decide what to do
with the plugin.
There are two problems:
1. Bad things happen with the Ruby ftplugin balloonexpr function.
Yours is the correct solution to #1. (If the plugin author is
unresponsive, it's up to Bram what to do.)
2. Netrw sets beval. (otherwise #1 wouldn't cause problems.)
It shouldn't do this. It's fine for it to set up a balloonexpr
function. It's not fine for it to turn on the ballooneval setting,
which should be left up to the user.
Hello,
Part of the problem from my viewpoint is that beval is a global setting
instead of being local. I have netrw v143m working around this; beval
is effectively set for netrw buffers only. You can still
let g:netrw_nobeval=1
in your .vimrc and suppress it entirely (via netrw, that is).
Regards,
Chip Campbell
--
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
