> Hi,
>
> For some reason I need to access some local service within vim, this can
> be Unix socket (d-bus, x message, etc.) or TCP socket (http, ftp, etc.).
>
> A typical example is an IM engine, which can provide service to both XIM
> and vimim. The engine may need a relatively long start-up time to build
> the cache and it only need to start once, while vim should start-up very
> fast and run many times. Separate them may be a good idea.
>
> I found nothing related to socket access or IPC feature in vim script so
> I cannot do that from within vim script. Seek for python or perl support
> is not an option here, since we should not add unnecessary dependency to
> end-users.
>
> 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.
>
> Any hints?
>
Vim already includes (if compiled with the proper features) two
mechanisms for inter-process communication:
- client-server operation (on both X11 and Windows)
:help remote.txt
- OLE (Windows only)
:help if_ole.txt
Best regards,
Tony.
--
I'm going to Boston to see my doctor. He's a very sick man.
-- Fred Allen
--
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
No comments:
Post a Comment