unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Richard Stallman <rms@gnu.org>
Cc: 53013@debbugs.gnu.org, Akira Kyle <akira@akirakyle.com>
Subject: bug#53013: 29.0.50; xwidget-webkit: SIGCHLD not being caught after xwidget-webkit buffer killed
Date: Fri, 07 Jan 2022 12:40:30 +0800	[thread overview]
Message-ID: <87v8ywyx8h.fsf@yahoo.com> (raw)
In-Reply-To: <E1n5gkW-0003OX-P1@fencepost.gnu.org> (Richard Stallman's message of "Thu, 06 Jan 2022 23:21:08 -0500")

Richard Stallman <rms@gnu.org> writes:

> Emacs does a lot of special things in handling subprocesses, and that
> is a very important feature.
>
> On general principles, I think that means we should perfect our own
> code rather than try to use code maintained by another project for
> this.

I'm not talking about replacing Emacs's own code with GLib's system
entirely, but just relying on GLib to tell us when a process exits,
instead of installing our own SIGCHLD handler.

Thanks.





  reply	other threads:[~2022-01-07  4:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-04 21:10 bug#53013: 29.0.50; xwidget-webkit: SIGCHLD not being caught after xwidget-webkit buffer killed Akira Kyle
2022-01-05  2:40 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-05  5:04   ` Akira Kyle
2022-01-07  4:21     ` Richard Stallman
2022-01-07  4:40       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-01-08  3:58         ` Richard Stallman
2022-01-08  4:37           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-09  3:54             ` Richard Stallman
2022-01-14  8:19     ` Lars Ingebrigtsen
2022-01-14  8:20   ` Lars Ingebrigtsen

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=87v8ywyx8h.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=53013@debbugs.gnu.org \
    --cc=akira@akirakyle.com \
    --cc=luangruo@yahoo.com \
    --cc=rms@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).