all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: matthew@mattleach.net, 12697@debbugs.gnu.org
Subject: bug#12697: 24.2; Emacs crashes when using it as the commit editor for git
Date: Mon, 22 Oct 2012 22:22:55 +0200	[thread overview]
Message-ID: <83bofucl40.fsf@gnu.org> (raw)
In-Reply-To: <m2d30az9qs.fsf@igel.home>

> From: Andreas Schwab <schwab@linux-m68k.org>
> Cc: matthew@mattleach.net,  12697@debbugs.gnu.org
> Date: Mon, 22 Oct 2012 19:39:55 +0200
> 
> >> now that emacs no longer puts itself and the terminal into its own
> >> process group.
> >
> > Did we have good reason to stop doing that?
> 
> IMHO no.  All the BSD_PGRPS stuff was removed on the premise that it
> wasn't used any more, but disabling BSD_PGRPS in s/gnu-linux.h was
> already questionable.

Come think about it, why not stop depending on SIGINT for quitting?
We already do that in GUI session (AFAIU), so why should TTY frames be
different?  We could just detect C-g in the SIGIO handler, no?

If this makes sense, then this whole issue would go away.  Of course,
we will then lose the "emergency exit" feature, but since core dumps
are reportedly disabled on many systems anyway, that doesn't sound
like too much of a loss, and GUI sessions already cannot use it
anyway.





  reply	other threads:[~2012-10-22 20:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-21 20:17 bug#12697: 24.2; Emacs crashes when using it as the commit editor for git Matthew Leach
2012-10-22  8:26 ` Andreas Schwab
2012-10-22 17:15   ` Eli Zaretskii
2012-10-22 17:39     ` Andreas Schwab
2012-10-22 20:22       ` Eli Zaretskii [this message]
2012-10-22 21:34         ` Andreas Schwab
2012-10-27  5:31 ` bug#12697: " Paul Eggert
2012-10-27  7:52   ` Eli Zaretskii
2012-10-28 18:57     ` Paul Eggert
2012-10-31 17:28 ` Paul Eggert

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=83bofucl40.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=12697@debbugs.gnu.org \
    --cc=matthew@mattleach.net \
    --cc=schwab@linux-m68k.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.