On 2016-02-08, Bram Moolenaar wrote:
> One problem that I haven't figured out yet: When starting a job using a
> shell, we get the PID of the shell. So we can kill the shell, but not
> the process that it started.
> E.g. "/bin/sh python demoserver.py <here >there". A shell is also
> useful for expanding wildcards, would be nice if we can make this work.
Starting the process with exec should fix that. That will replace
the shell with the job, giving the job the same PID as the shell.
Your example would then become:
/bin/sh exec python demoserver.py <here >there
Regards,
Gary
--
--
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
