Re: [patch] fix #1155 (A job cannot be stopped right after being started)

2016-10-17 Fir de Conversatie Ozaki Kiichi
> Seems like a reasonable solution. So the test fails for the current > Vim? Or does it fail sometimes? Sometimes. Especially, according to travis-ci, it is highly probable to fail on Mac; about half or more. -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type y

Re: [patch] fix #1155 (A job cannot be stopped right after being started)

2016-10-17 Fir de Conversatie Bram Moolenaar
Ozaki Kiichi wrote: > The following will fix #1155. > > https://gist.github.com/ichizok/26d571401be0685267ebf0790e964903 > > [cause of problem] > > This problem may occur on some *nix environment. > > Calling job_stop immediately after job_start, child process may receive signal > before rese

[patch] fix #1155 (A job cannot be stopped right after being started)

2016-10-17 Fir de Conversatie Ozaki Kiichi
Hi. The following will fix #1155. https://gist.github.com/ichizok/26d571401be0685267ebf0790e964903 [cause of problem] This problem may occur on some *nix environment. Calling job_stop immediately after job_start, child process may receive signal before reset_signals(). Therefore deadly-signals