From: Peter Stephenson <p.stephenson@samsung.com>
To: "zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: long-standing tty related issue: wrapped Emacs not suspended
Date: Wed, 26 Sep 2018 14:41:35 +0100 [thread overview]
Message-ID: <20180926134137eucas1p26be62f4fbdd1806b2b0754e10e3dee83~X9u1oru3x1893618936eucas1p2n@eucas1p2.samsung.com> (raw)
In-Reply-To: <CAH+w=7ZmhsKwJTSU90gDrZy1FgJQDAfkYaLMmY8Eq=aSAYdQwg@mail.gmail.com>
On Tue, 25 Sep 2018 22:47:44 -0700
Bart Schaefer <schaefer@brasslantern.com> wrote:
> On Tue, Sep 25, 2018 at 3:38 AM Peter Stephenson
> But if you ^Z a function and then background it, the parent still
> believes it to be running even though it has instantly stopped:
Yes, I mentioned that problem --- it's not new, at least 5.5 behaved
that way, and it's related to the fact that we have STAT_NOPRINT
associated with the subjob, which is what's actually being suspended.
I'm not sure how to fix this without unleashing a torrent of new
messages, but it's possible the key is ensuring the superjob and subjob
are aligned and printing a message if we update both --- since the point
here is to pretend to the user that they're acting as a single job.
(They bloody aren't, I can tell you...)
pws
next prev parent reply other threads:[~2018-09-26 13:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-20 12:30 Vincent Lefevre
2018-09-20 15:43 ` Joey Pabalinas
2018-09-20 23:10 ` Vincent Lefevre
2018-09-21 16:57 ` Peter Stephenson
2018-09-21 23:14 ` Joey Pabalinas
2018-09-22 1:17 ` Bart Schaefer
2018-09-22 5:51 ` Joey Pabalinas
2018-09-22 18:54 ` Vincent Lefevre
2018-09-22 21:27 ` Joey Pabalinas
2018-09-23 7:21 ` Vincent Lefevre
2018-09-24 19:51 ` Peter Stephenson
2018-09-25 10:37 ` Peter Stephenson
2018-09-25 17:04 ` Daniel Shahaf
2018-09-26 5:47 ` Bart Schaefer
2018-09-26 13:41 ` Peter Stephenson [this message]
2018-09-26 15:17 ` Peter Stephenson
[not found] ` <20180926161708.39be6402@camnpupstephen.cam.scsc.local>
2018-10-02 15:32 ` Peter Stephenson
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='20180926134137eucas1p26be62f4fbdd1806b2b0754e10e3dee83~X9u1oru3x1893618936eucas1p2n@eucas1p2.samsung.com' \
--to=p.stephenson@samsung.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).