From: Richard Stallman <rms@gnu.org>
Cc: bug-gnu-emacs@gnu.org
Subject: Re: comint-interrupt-subjob failure
Date: Sat, 27 Apr 2002 16:42:05 -0600 (MDT) [thread overview]
Message-ID: <200204272242.g3RMg5o05589@aztec.santafe.edu> (raw)
In-Reply-To: <200204260215.g3Q2FSA29126@Manresa.AI.SRI.COM> (message from Mabry Tyson on Thu, 25 Apr 2002 19:15:28 -0700 (PDT))
M-x shell (my shell is tcsh)
Then do something that takes time to run like
/usr/sbin/traceroute www.bbc.co.uk
Then type ^C^C (which is bound to comint-interrupt-subjob)
I then see a shell prompt, but the traceroute process is still running
and producing output and shows up in jobs.
This would seem to be a shell bug. It is clear that the signal was
delivered. Since the shell resumed, it must have receive SIGCLD.
prev parent reply other threads:[~2002-04-27 22:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-26 2:15 comint-interrupt-subjob failure Mabry Tyson
2002-04-27 22:42 ` Richard Stallman [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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200204272242.g3RMg5o05589@aztec.santafe.edu \
--to=rms@gnu.org \
--cc=bug-gnu-emacs@gnu.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.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).