> Uhm. So vim-remote has nothing to do with the remote* calls that are
> built into Vim? That is extremely confusing.
For example, if you want to write vimscript like client-server like
application.
vim => server => vim
You can write server's code in any language. However, server should work as
thread or forked-process.
When server send reply to vim from thread, vim will be crash. because, vim
is not thread-safe.
VIM1 =(if_python)=> server =(remote_expr)=> VIM1
And forked process don't have way to send replies.
(of course, we know vim have '--remote-expr' argument, but it's too heavy
for only sending replies.)
VIM1 =(perl and fork())=> server =(system('vimremote ...'))=> VIM1
Then, we often use vim-remote call for sending replies light weight.
This is very useful for writing asynchronized application.
BTW)
For linux version of vim, remote call depend on x11.
Then, Yukihiro Nakadaira(author of vim-remote) began to improvement vim
itself.
http://code.google.com/r/yukihironakadaira-vim-cmdsrv-nox/
This don't use x11 protocol. it use unix-domain socket for unix.
And for windows, it use named pipe. This will be very useful functions.
Thanks.
At the last, sorry for my poor english.
- Yasuhiro Matsumoto
--
You received this message from the "vim_mac" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
