From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: call-process vs start-process
Date: Tue, 25 Jun 2002 19:33:42 -0400 [thread overview]
Message-ID: <E17Mzoc-0000CD-00@fencepost.gnu.org> (raw)
In-Reply-To: <200206241421.aa27980@gremlin-relay.ics.uci.edu> (message from Dan Nicolaescu on Mon, 24 Jun 2002 14:21:11 -0700)
When using `start-process' the child process seems to be killed by a
SIGHUP from emacs. Is this OK? Is emacs supposed to send SIGHUP to the
child process?
I believe this is normal. Emacs does not explicitly send SIGHUP. It
probably results from Emacs's closing the pty.
next parent reply other threads:[~2002-06-25 23:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200206241421.aa27980@gremlin-relay.ics.uci.edu>
2002-06-25 23:33 ` Richard Stallman [this message]
2002-06-26 14:15 ` call-process vs start-process Stefan Monnier
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=E17Mzoc-0000CD-00@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@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).