On 2018/12/02 16:52, Olivier Taïbi wrote:
> On Thu, Nov 29, 2018 at 11:00:18PM +, Stuart Henderson wrote:
> > On 2018/11/29 17:36, George Koehler wrote:
> > > On Thu, 29 Nov 2018 09:38:31 +0100
> > > Olivier Taïbi wrote:
> > >
> > > > 2) remove the check
> > > > if (job_pid ==
On Thu, Nov 29, 2018 at 11:00:18PM +, Stuart Henderson wrote:
> On 2018/11/29 17:36, George Koehler wrote:
> > On Thu, 29 Nov 2018 09:38:31 +0100
> > Olivier Taïbi wrote:
> >
> > > 2) remove the check
> > > if (job_pid == getpgid(job_pid))
> > > from vim's mch_signal_job() in
On 2018/11/29 17:36, George Koehler wrote:
> On Thu, 29 Nov 2018 09:38:31 +0100
> Olivier Taïbi wrote:
>
> > 2) remove the check
> > if (job_pid == getpgid(job_pid))
> > from vim's mch_signal_job() in src/os_unix.c so that the whole group
> > always gets a signal.
>
> Thank you for
On Thu, 29 Nov 2018 09:38:31 +0100
Olivier Taïbi wrote:
> 2) remove the check
> if (job_pid == getpgid(job_pid))
> from vim's mch_signal_job() in src/os_unix.c so that the whole group
> always gets a signal.
Thank you for finding the failing getpgid(). I suggest to remove the
check, like
vim lets you (and plugins) start and stop processes using job_start and
job_stop. There is an issue: stopping does not work, see for example
https://github.com/lervag/vimtex/issues/1032
in the case of the vimtex plugin. This is because the function
mch_signal_job in vim's src/os_unix.c first
