I’ve stumbled over a rather odd issue while playing around with my Neobundle and Unite.vim plugin configurations: both the ':Unite neobundle/search' command and the ':Unite file' command with the selecta sorter enabled have been spewing script errors at me (about using Floats as string in some deep nested functions), which, as I tried to find their source by progressively disabling all my plugins and settings, turned out to **only be present when MacVim is launched via the .app bundle**.
OTOH, when launching MacVim via the terminal, i.e. via the `mvim` script or manually as `/path/to/MacVim.app/Contents/MacOS/Vim -g`, none of these errors appear. At all. The only difference in the scenarios I can find on superficial analysis is the process ownership Activity Monitor displays: * when launched via the app bundle, the Vim process is owned by MacVim, which is owned by launchd, and the errors occur; * when launched from the terminal, the reverse is true, i.e. the MacVim process is owned by the Vim process, which is owned by launchd, and no errors occur. Nothing else I do (bypassing vimrc and gvimrc via `-u NONE`and `-U NONE`, selectively disabling plugins, loading files or working on empty buffers, calling the incrimated plugins via mappings or via command) does make the least difference. The selecta sorter uses ruby, but in both cases, MacVim uses the Mavericks system ruby, and the neobundle/search source is VimL all the way, so I’m at loss as to what is happening here… -- -- You received this message from the "vim_mac" 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 --- You received this message because you are subscribed to the Google Groups "vim_mac" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
