On 5 January 2011 16:58, Anders Janmyr <[email protected]> wrote: > Hi Bharat, thanks for your reply. > > I should have been better at describing my problem. > > It comes up when I start vim from the terminal. > > $ rvm use 1.9.2 > $ mvim Gemfile #for example > > Then when I use omnicompletion in insert mode and try to do a <TAB> or > a CTRL-n it crashes. > > Vim: Caught deadly signal SEGV > Vim: preserving files... > Vim: Finished. > > If I start vim as an App it works out fine. > > $ rvm use system > $ mvim Gemfile # also works out fine > > > But I want to start it from the command line with the correct version > of ruby set... > But it is not killing me, it is just annoying :(
I'm not sure exactly how rvm works, but I am pretty sure that when you start vim "as an App" it is still using the system Ruby version (which may or may not be what you want). Using "mvim" may work as long as you don't call it from the same Terminal window/tab that you called "rvm" from (I am guessing here). It is not possible to have one MacVim binary that works with several different versions of Ruby at once since it links to a specific version at build time. Patching MacVim to dynamically load a specific version of Ruby will require some effort (there was a similar discussion about loading Python in the past on vim_dev if I remember correctly). Björn -- 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
