* Stephan Kulow <[email protected]> [Jan 10. 2014 08:45]: > On 09.01.2014 21:48, Josef Reidinger wrote: > > > > Yes, it looks like. So how can we proceed? Disable ruby interface to > > vim? Or change dynamic to common link to ruby? I don't have enough > > knowledge to fix it and google doesn't show me any solution. > > > I checked what vim is doing there and it's hacking *deeply* into the > ruby internals by overwriting functions and #define variables and such. > > It's very likely that this will not work even if you fix the linking. So > disable it as long as vim upstream hasn't picked up ruby 2.1 (actually > it requires ruby 1.9.1...)
Actually, it's rather straightforward to fix it. Expect a patch soon. Klaus -- SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Maxfeldstraße 5, 90409 Nürnberg, Germany -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
