From: Joey Pabalinas <joeypabalinas@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Peter Stephenson <p.w.stephenson@ntlworld.com>,
"zsh-workers@zsh.org" <zsh-workers@zsh.org>,
Joey Pabalinas <joeypabalinas@gmail.com>
Subject: Re: long-standing tty related issue: wrapped Emacs not suspended
Date: Fri, 21 Sep 2018 19:51:48 -1000 [thread overview]
Message-ID: <20180922055148.dvmf7kvknnez3cvd@gmail.com> (raw)
In-Reply-To: <CAH+w=7Z_xB9uXHHuPs59bxMaufCDRFcBp8cs-94Ebr3ggYjS0g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1391 bytes --]
On Fri, Sep 21, 2018 at 06:17:47PM -0700, Bart Schaefer wrote:
> FWIW I can't get what Vincent describes to happen at all with the
> above example and the current git checkout, even after assorted
> bg/fg/^Z/etc. But the system on which I can currently test doesn't
> have an X-enabled emacs.
This did confuse me a bit earlier in Peter's email, as I also had this
exact behavior on 5.5.1.r143.g225b35c9070f94cf79 where -CONT didn't even
seem to work regardless of which child process I sent it to. I had just
chalked it up to one of my weird configs, but I guess this is pretty
much happening to everyone running the development versions?
> Also, the parent shell should probably be sending a SIGCONT to all
> those jobs whenever they are fg'd, even if it believes they are
> already running. SIGCONT is harmless for a job that is not stopped,
> and trusting the job table idea of the process state is an unnecessary
> optimization.
Interestingly enough I did once run into a program that used a SIGCONT
handler, reset to default disposition in SIGTSTP handler, for some internal
callback-ish stuff. My guess was it assumed SIGCONT to be a "safe" sentinel
signal (while completely forgetting about its uncatchable brother SIGSTOP),
but cases like that are mostly just broken curiosities and definitely not
worth worrying about :)
--
Cheers,
Joey Pabalinas
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-09-22 5:52 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 [this message]
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
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=20180922055148.dvmf7kvknnez3cvd@gmail.com \
--to=joeypabalinas@gmail.com \
--cc=p.w.stephenson@ntlworld.com \
--cc=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).