Brian Burns wrote:
> > While you are digging into this, could you find some way to test this
> > code? This might be complicated, since it requires starting two Vim
> > instances talking to each other, but it would be very useful to have at
> > least basic testing for this code.
> >
> >
>
> Hey,
>
> I've attached some basic tests.
> I'm not sure if what I'm doing here would work on all systems,
> but it's a start. Let me know what you think.
Thanks. It's nice to have a test for this, there was nothing before.
It is rather Unix-specific, but that's hard to avoid. We can only run
this test from the Unix Makefile so that we don't even try on other
systems.
Even the Unix version may not have the clientserver feature. We can
check that at the start:
STARTTEST
:so small.vim
:" drop out when the clientserver features is not supported
:if !has("clientserver")
: e! test.ok
: w! test.out
: qa!
:endif
If the test fails halfway then the test server keeps running. I think
it's better to kill it from the Makefile.
You can use v:progname for the Vim program name. It doesn't include the
path though.
--
hundred-and-one symptoms of being an internet addict:
101. U can read htis w/o ny porblm and cant figur eout Y its evn listd.
/// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
You received this message from the "vim_dev" 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
