git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Topics currently in the Stalled category

From
Jeff King <peff@peff.net>
Date
Nov 21, 2012, 20:13 UTC
Message-ID
<20121121201348.GG16280@sigill.intra.peff.net>
In-Reply-To
<7va9ua20nz.fsf@alter.siamese.dyndns.org>
On Wed, Nov 21, 2012 at 11:53:04AM -0800, Junio C Hamano wrote:
Show 8 quoted lines
> Jeff King <peff@peff.net> 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
> ;-)

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
Previous: Junio C Hamano
Message 6 of 6 in “Re: Topics currently in the Stalled category”
  1. Paul FoxNov 21, 2012
  2. Krzysztof MazurNov 21, 2012
  3. Jeff KingNov 21, 2012
  4. Paul FoxNov 21, 2012
  5. Junio C HamanoNov 21, 2012
  6. Jeff KingNov 21, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.