Hi, I have been getting multiple reports regarding the ballooneval feature, in particular with regards to editing Ruby files. The problem was originally reported on the MacVim issue tracker [1] but on my request was also posted here [2] but that post never got any attention so I am bringing it up once again.
The problem is that the ballooneval expression for Ruby gives an error and this error pops up in the balloon. I know of two proposed "fixes": 1) replace “ri -f simple -T” with “ri -f bs” as suggested in [3] 2) get rid of the ballooneval expression altogether as in [4] The plugin author is apparently not responding to emails. This issue raises a general question on how to deal with ballooneval in plugins. I've seen a few plugins that enable ballooneval if Vim was compiled with this feature and I think this needs to change at least for the plugins that are shipped with Vim. I say leave it up to users if they want to enable balloons or not -- don't force it upon them. For example, looking at [1] you see one case where the (buitin) netrw plugin is enabling ballooneval behind the users back. I see that there is a variable to _disable_ beval in netrw, but I argue it should be the other way around (set the variable if you want beval enabled, else leave it disabled). Anyway, I'd be very grateful if the first issue with beval in the ruby plugin could be fixed to begin with. It has been around for a long time and I've seen many complaints about this. I propose applying the patch in [4] to get rid of beval altogether. Thanks, Björn [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 -- 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
