Yukihiro Nakadaira wrote:
> On Wed, Feb 24, 2016 at 8:11 PM, mattn <mattn...@gmail.com> wrote:
>
> > I'm thinking "kill" is not matter for this test because this test should
> > be checking of exit.
> >
> > diff --git a/src/testdir/test_channel.vim b/src/testdir/test_channel.vim
> > index 69922b1..e74e54c 100644
> > --- a/src/testdir/test_channel.vim
> > +++ b/src/testdir/test_channel.vim
> > @@ -483,6 +483,7 @@ func Test_exit_callback()
> > if has('job')
> > call s:run_server('s:test_exit_callback')
> >
> > + call job_stop(s:exit_job, "kill")
> > " the job may take a little while to exit
> > sleep 50m
> >
>
> In CUI Vim, job_stop(job, "hup") doesn't work because AttachConsole() fails.
> The following patch might fix it. Job process is created in same console.
> I'm not sure if it doesn't causes another problem.
There is a todo item to make it possible to start a terminal for the job
to run in. This is especially useful if the job produces some output
and perhaps even prompts for input. We don't want that to get mixed up
with the Vim display.
So hopefully we can make both work. This would require the job to be
started with a socket, so its stdin/stdout go to the terminal.
--
Why isn't there mouse-flavored cat food?
/// 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.
