On 18/07/09 17:21, Marc Weber wrote: > > Excerpts from Tony Mechelynck's message of Sat Jul 18 16:01:20 +0200 2009: >> This said, IIUC Vim is basically a single-threaded application. Threads >> can (I think) only happen due to interfaces with threaded interpreters. > Ah thanks, I'll try to add pthread_getthreadid_np to verify this. > This explains a lot. > Yes. I'd like to add threading support. for Python it does already work > very well (At least vim doesn't crash).. > > I also checked ruby. However I don't know why ruby doesn't call back > into vim betwenn :ruby calls. So there is no problem at all. > However I'd like ruby being able to tell vim sth. without waiting for a > :ruby command. > > Marc Weber
There are also :rubydo and :rubyfile. How are the various functions, objects and variables of the VIM module implemented? (see ":help ruby-vim" and below) Best regards, Tony. -- hundred-and-one symptoms of being an internet addict: 81. At social functions you introduce your husband as "my domain server." --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
