s:rubypath in ftplugin/ruby.vim

Mark Guzman segfault at hasno.info
Tue Jan 23 14:43:55 EST 2007


Tim Pope wrote:
> A little further investigation reveals the trigger.  The first time
> the Ruby interface is used is significant.  If it is used at the top
> level, all is well.  If it is nested deep inside several function
> calls, this seems to reduce the available stack space to Ruby.  Note
> that only there very first call is relevant.  If I add
>
> silent! ruby nil
>
> to the plugin initialization function of rails.vim (so that the call
> is nested just one function deep), everything works great.  I'm not
> thrilled with forcing initialization at each start but I can't find a
> better place to do it.
>   
I wonder if the same thing happens with the other interfaces.
> This does not help my segfaulting acquaintance (whom I wlll hereafter
> refer to as jsunn) though.  I still think use of the interface in the
> ftplugin should be limited to Windows.
>   
I'm fine with that, it doesn't really bother me anywhere other than 
windows. Though wouldn't that handle the initialization issue for you?

Thanks Tim
  --mark


More information about the vim-ruby-devel mailing list