From: Dan Jacobson <jidanni@jidanni.org>
Subject: Re: compile kills background jobs undocumentedly
Date: Mon, 02 Feb 2004 07:48:30 +0800 [thread overview]
Message-ID: <87llnme4z5.fsf@jidanni.org> (raw)
In-Reply-To: <401AE88E.7020905@yahoo.com> (Kevin Rodgers's message of "Fri, 30 Jan 2004 16:28:14 -0700")
K> ...calls delete-process, which calls Fkill_process, which sends a QUIT
K> signal. So I don't see why ignoring HUP would have any effect on that
K> sequence of actions.
All I know is it works here on Debian.
BTW, every once in a while, in the standard compile situation, a
running job isn't noticed, and not asked about or killed, so we get a
concurrent 2nd job. Can't reproduce it.
prev parent reply other threads:[~2004-02-01 23:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-29 21:47 compile kills background jobs undocumentedly Dan Jacobson
2003-12-21 21:19 ` Dan Jacobson
2004-01-29 4:45 ` Dan Jacobson
2004-01-30 23:28 ` Kevin Rodgers
2004-02-01 23:48 ` Dan Jacobson [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=87llnme4z5.fsf@jidanni.org \
--to=jidanni@jidanni.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).