From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: zsh-workers@zsh.org
Subject: Re: jobs -r doesn't show jobs continued by kill -CONT
Date: Tue, 5 May 2015 20:14:11 +0100 [thread overview]
Message-ID: <20150505201411.3170277f@ntlworld.com> (raw)
In-Reply-To: <150505120214.ZM18560@torch.brasslantern.com>
On Tue, 5 May 2015 12:02:14 -0700
Bart Schaefer <schaefer@brasslantern.com> wrote:
> Is there compound-command weirdness that's going to show up as a result
> of changing jn->stat along with pn->status if there is more than one
> process per job?
Yes, if only a subset of them get the SIGCONT.
Don't do that.
[Now performing the "hear no evil, see no evil, speak no evil"
ritual purification.]
pws
prev parent reply other threads:[~2015-05-05 19:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-03 22:52 Han Pingtian
2015-05-04 6:26 ` Bart Schaefer
2015-05-04 17:36 ` Peter Stephenson
2015-05-05 19:02 ` Bart Schaefer
2015-05-05 19:14 ` Peter Stephenson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150505201411.3170277f@ntlworld.com \
--to=p.w.stephenson@ntlworld.com \
--cc=zsh-workers@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).