Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: long-standing tty related issue: wrapped Emacs not suspended
- X-seq: zsh-workers 43559
- From: Peter Stephenson <p.stephenson@xxxxxxxxxxx>
- To: "zsh-workers@xxxxxxx" <zsh-workers@xxxxxxx>
- Subject: Re: long-standing tty related issue: wrapped Emacs not suspended
- Date: Wed, 26 Sep 2018 14:41:35 +0100
- Cms-type: 201P
- Dkim-filter: OpenDKIM Filter v2.11.0 mailout1.w1.samsung.com 20180926134138euoutp017270bc34fedfff80d626d06d83b26bda~X9u22_gYS1531415314euoutp01v
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=samsung.com; s=mail20170921; t=1537969298; bh=Tv1LbEyFJVmjgtFRJL1P9fB5ZEhOLHWA7iszWKd5Xxs=; h=Date:From:To:Subject:In-Reply-To:References:From; b=nPCEuhgMTUSA6pgI1FR+BzwFJJNk/kIVvzWVLOZsfz5LY2tI3lJ8reDiQmc0htxkN ZfecyHrXBq8gkC+vyDMM0uQh0adbjgRuN5o8tYoWQFEYIyc00c9U87l3RZtW1ibTqV Nd2wnBjj2nItiX4xyNf+gnOBb6rHX+dcMKKKkXog=
- In-reply-to: <CAH+w=7ZmhsKwJTSU90gDrZy1FgJQDAfkYaLMmY8Eq=aSAYdQwg@mail.gmail.com>
- List-help: <mailto:zsh-workers-help@zsh.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- List-unsubscribe: <mailto:zsh-workers-unsubscribe@zsh.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- Organization: SCSC
- References: <20180920123005.GA20647@zira.vinc17.org> <20180921175740.6ab97a81@pws-HP.localdomain> <CGME20180924200327epcas5p16c59687fb2a9ac2ea8919ceab7705c02@epcas5p1.samsung.com> <20180924205106.03ee3da6@pws-HP.localdomain> <20180925103759eucas1p2a15709c7a9d8df72d8c390521a6999ab~XnlOUhOUG3250532505eucas1p2u@eucas1p2.samsung.com> <CAH+w=7ZmhsKwJTSU90gDrZy1FgJQDAfkYaLMmY8Eq=aSAYdQwg@mail.gmail.com>
On Tue, 25 Sep 2018 22:47:44 -0700
Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx> 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
Messages sorted by:
Reverse Date,
Date,
Thread,
Author