> be Unix socket (d-bus, x message, etc.) or TCP socket (http, ftp, etc.).
Locking on platform-specific stuff like dbus, you effectively lose one of the main Vim advantages: its multiplatformness. Designing some sort of universal IPC mechanisms would be quite challenging task. > Adding IPC support seems no problem for vim design philosophy, since > this enables vim interact with other applications better, instead of > incorporating other application features into vim itself. Vim is single-threaded application. If you want to implement proper IPC, for instance, Vim waiting on some event, you will need to rewrite much of its core I'm afraid. -- Sergey Khorev http://sites.google.com/site/khorser Can anybody think of a good tagline I can steal? -- You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php
