Omni completion stack overflow
dougkearns at gmail.com
Sun Feb 18 21:08:56 EST 2007
On Tue, Feb 13, 2007 at 10:31:37AM -0500, Mark Guzman wrote:
> Doug Kearns wrote:
> > Thanks for that, I managed to overlook your explanation in the
> > "s:rubypath in ftplugin/ruby.vim" thread.
> > Initializing the interface in my vimrc does seem to eliminate the
> > problem but running the omni completion script alone is enough to
> > trigger it (ie. when my ~/.vim contains only the vim-ruby runtime
> > files).
> > Has this general problem been reported 'upstream'?
> No, this hasn't been mentioned on vim-dev so far, I'll do so now.
> So far it has all been related back to the stack issue, all of the
> people I've debugged with have had older versions of rails.vim installed.
So am I the only one that can reproduce it with a clean Vim7
installation and the latest rubycomplete.vim? I don't and never have
had rails.vim installed. I've never even downloaded it. ;-)
More information about the vim-ruby-devel