From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Colascione <dan.colascione@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] Unconditional quit on SIGUSR2
Date: Mon, 28 Mar 2011 07:48:42 -0400 [thread overview]
Message-ID: <E1Q4Aw6-0005Uu-3p@fencepost.gnu.org> (raw)
In-Reply-To: <4D90354E.9000704@gmail.com> (message from Daniel Colascione on Mon, 28 Mar 2011 00:14:22 -0700)
> Date: Mon, 28 Mar 2011 00:14:22 -0700
> From: Daniel Colascione <dan.colascione@gmail.com>
>
> Sometimes Emacs gets stuck in places where quitting is suppressed,
> such as during redisplay. For most users, the only way to deal with
> this situation is to abruptly terminate Emacs.
>
> This patch allows users to recover from this situation by sending Emacs
> a SIGUSR2 signal. When we receive it, we set debug-on-quit to t,
> inhibit-quit to nil, and quit-flag to t. These operations will force
> Emacs to stop at the next possible opportunity and display a backtrace.
> From here, users can save their work, and developers can figure out
> what caused the hang.
If the goal is to provide a way for the user to interrupt a stuck
Emacs in a way that allows to save edits or debug Emacs, then users
can already send SIGTERM and developers can already attach a debugger,
and that will achieve the same result. Why do we need a new machinery
to do something that is already possible via essentially the same
sequence of actions, i.e. type "kill EMACS-PID" at the shell prompt?
Or am I missing something?
Btw, did you actually test the possibility to interrupt a stuck
redisplay using this patch? I'm asking because I think redisplay
cannot be interrupted like that: it never checks the quit flag, and
for a good reason AFAIK -- you cannot interrupt it at an arbitrary
point without disastrous consequences. If we want to make redisplay
interruptible, we need to add code to it in strategic places. Again,
I don't see a need for doing this, unless someone shows a convincing
use case where such a feature would be useful.
Apologies if I missed something obvious, and thanks for working on
this.
next prev parent reply other threads:[~2011-03-28 11:48 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-28 7:14 [PATCH] Unconditional quit on SIGUSR2 Daniel Colascione
2011-03-28 11:48 ` Eli Zaretskii [this message]
2011-03-28 12:32 ` Julien Danjou
2011-03-28 14:32 ` Eli Zaretskii
2011-03-28 14:49 ` Julien Danjou
2011-03-28 13:38 ` Daniel Colascione
2011-03-28 14:47 ` Eli Zaretskii
2011-03-28 17:23 ` Daniel Colascione
2011-03-28 18:37 ` Eli Zaretskii
2011-03-28 19:29 ` Daniel Colascione
2011-03-28 19:41 ` Eli Zaretskii
2011-03-28 19:49 ` Daniel Colascione
2011-03-28 19:52 ` Lennart Borgman
2011-03-28 19:56 ` Daniel Colascione
2011-03-28 20:06 ` Lennart Borgman
2011-03-28 20:12 ` Daniel Colascione
2011-03-28 20:45 ` Lennart Borgman
2011-03-28 21:13 ` In praise of font-lock (Was: Re: [PATCH] Unconditional quit on SIGUSR2) Daniel Colascione
2011-03-28 21:27 ` Lennart Borgman
2011-03-28 20:10 ` [PATCH] Unconditional quit on SIGUSR2 chad
2011-03-28 22:00 ` Eli Zaretskii
2011-03-28 22:08 ` Daniel Colascione
2011-03-28 22:20 ` chad
2011-03-29 17:55 ` Daniel Colascione
2011-03-29 18:14 ` Daniel Colascione
2011-04-25 2:16 ` Daniel Colascione
2011-04-25 9:23 ` joakim
2011-04-25 9:33 ` Daniel Colascione
2011-04-25 13:32 ` Stefan Monnier
2011-04-25 18:21 ` Daniel Colascione
2011-04-25 18:43 ` Stefan Monnier
2011-04-26 14:47 ` Richard Stallman
2011-03-29 13:23 ` Tom Tromey
2011-03-29 14:25 ` Stefan Monnier
2011-03-29 14:47 ` Tom Tromey
2011-03-29 21:37 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1Q4Aw6-0005Uu-3p@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=dan.colascione@gmail.com \
--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 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.