Lcd wrote:
> On 3 February 2016, Danek Duvall <duv...@comfychair.org> wrote:
> [...]
> > I think the most reliable thing to do here is to have a way to know
> > the pid and kill it directly, but since ! goes through a shell, you
> > don't have any way of knowing what the pid of test_channel.py is.
>
> Or just make the server write its PID to a file with an unique name.
> This is still not ideal, but it's probably good enough for tests.
Like we do for the port number. OK, that can work for now. But we need
job control functionality anyway. We should use that once it's
implemented.
Vim can already start jobs, but currently always waits for them to
finish (with "!cmd" or system("cmd")). Should not be too difficult to
run a job in the background and get its PID. At least on Unix, not sure
about MS-Windows.
--
"A clear conscience is usually the sign of a bad memory."
-- Steven Wright
/// Bram Moolenaar -- b...@moolenaar.net -- 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
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
