From: Bart Schaefer <schaefer@brasslantern.com>
To: "zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: long-standing tty related issue: wrapped Emacs not suspended
Date: Tue, 25 Sep 2018 22:47:44 -0700 [thread overview]
Message-ID: <CAH+w=7ZmhsKwJTSU90gDrZy1FgJQDAfkYaLMmY8Eq=aSAYdQwg@mail.gmail.com> (raw)
In-Reply-To: <20180925103759eucas1p2a15709c7a9d8df72d8c390521a6999ab~XnlOUhOUG3250532505eucas1p2u@eucas1p2.samsung.com>
On Tue, Sep 25, 2018 at 3:38 AM Peter Stephenson
<p.stephenson@samsung.com> wrote:
>
> As before, the only way of teasing out problems will be to try this out,
> so I'll commit it.
Minor nit -- if a normal background job gets stopped by a signal, the
shell reports it:
% e &
[1] 2936
%
[1] + suspended (tty output) e
But if you ^Z a function and then background it, the parent still
believes it to be running even though it has instantly stopped:
% e
zsh: suspended e
% bg
[1] + continued e
% jobs
[1] + running e
% ps a
PID TT STAT TIME COMMAND
2813 s003 S 0:00.09 Src/zsh -f
2906 s003 T 0:00.21 emacs
2908 s003 T 0:00.00 Src/zsh -f
2917 s003 R+ 0:00.00 ps a
The right thing happens if you "fg" it again (it gets sent a SIGCONT,
and the parent waits) so this isn't critical, but it's potentially
confusing.
next prev parent reply other threads:[~2018-09-26 5:48 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 [this message]
2018-09-26 13:41 ` Peter Stephenson
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='CAH+w=7ZmhsKwJTSU90gDrZy1FgJQDAfkYaLMmY8Eq=aSAYdQwg@mail.gmail.com' \
--to=schaefer@brasslantern.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).