> Excerpts from Ben Fritz's message of Thu Feb 16 16:41:35 +0100 2012:
> > I don't think you can. What's wrong with client-server?
> It requires X.
>
> I only know about
> - python threads (crashes vim if you call back into vim)
> - ruby threads (not sure, probably crashes Vim as well)
> - scheme threads (they seem to be thread save, at least lot's of C code
> exists for all gui backends and console vim)
> (-> if_mzsch)
> - :h netbeans (eg used by the pyclewn.sourceforge.net project)
>
> If you find another way I'd be surprised. See documentation about
> vim-addon-async also talking about barts patch [1] for vim.
> I don't think that we all would have spend such much time finding
> workarounds if Vim had a clean API.
That's true. To Ben: the problem with client-server on windows is that
whenever I call it it opens a new window with error code, even if the error
code is 0, which is a result of vim implementation on windows (as far as
I know). This makes a problem when you want to run it few times and you don't
want to mess user space with error codes. On linux or mac with X it
works fine though.
>
> So use those workarounds, switch editor or get your hands dirty and
> implement the missing feature. And doing that proberly requires you
> testing 2-3 different gui implementations of Vim (see if_mzsch
> implementation).
Unfortunately, I'm not a C programmer (yet ;) ).
>
> http://github.com/bartman/vim (non gui only) This patch made me finally
> write vim-addon-async because I wanted my code to work without
> recompiling vim or depending on very new console only features.
>
> You can also digg in vim_dev me asking for such feature before spending
> all that time. So I'm pretty sure that there is no way.
>
> Marc Weber
>
> --
> You received this message from the "vim_use" 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
Thanks,
Marcin
--
You received this message from the "vim_use" 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
No comments:
Post a Comment