2 messages, 2 authors, 2016-06-15 · open the first message on its own page
From: Junio C Hamano <hidden>
Date: 2016-06-15 22:55:23
Jeff King [off-list ref] writes:
[1] Given the core-dumping behavior of SIGQUIT, I suspect it is not
nearly as widely used as SIGINT, but it sounds more like the
principle of least surprise to treat them the same.Sounds sensible. I wonder what happens when the editor is suspended ;-)
From: Jeff King <hidden>
Date: 2016-06-15 22:55:23
On Wed, Nov 21, 2012 at 11:53:04AM -0800, Junio C Hamano wrote:
Jeff King [off-list ref] writes:quoted
[1] Given the core-dumping behavior of SIGQUIT, I suspect it is not nearly as widely used as SIGINT, but it sounds more like the principle of least surprise to treat them the same.Sounds sensible. I wonder what happens when the editor is suspended ;-)
I think we would want to leave SIGTSTP alone; the editor should typically respect it, and we would want to also pause until we get SIGCONT (although even if we did continue, we would just be blocking on wait() for the editor, anyway, so it is not a big deal). Implicit in my "least surprise" comment above is that handling SIGQUIT would match what system(3) does, so it makes sense to me to match that (it also blocks SIGCHLD, but I do not think that really matters from a user-visible perspective). -Peff