> On Sun, Nov 11, 2012 at 11:31:00AM -0500, Jeff King wrote:
> > Here's a series that I think should resolve the situation for everybody.
> > [1/5]: launch_editor: refactor to use start/finish_command
> > The cleanup I sent out a few minutes ago.
> > [2/5]: launch_editor: ignore SIGINT while the editor has control
> > Paul's patch rebased on my 1/5.
> > [3/5]: run-command: drop silent_exec_failure arg from wait_or_whine
> > [4/5]: run-command: do not warn about child death by SIGINT
> > [5/5]: launch_editor: propagate SIGINT from editor to git
> > Act more like current git when the editor dies from SIGINT.
> Looks ok, but what about SIGQUIT? Some editors like GNU ed (0.4 and 1.6)
> ignore SIGQUIT, and after SIGQUIT git dies, but editor is still running.
> After pressing any key ed receives -EIO and prints "stdin: Input/output
> error". GNU ed 1.6 then exits, but ed 0.4 prints this error forever.
> Maybe git should kill the editor in such case?
there's certainly lots of precedent for treating SIGINT and SIGQUIT
the same. but there's also some merit to saying that if the user
knows to send SIGQUIT instead of SIGINT, they may well have a reason.
(after all, if we always treat them the same, there's no point in
the em editor (linus' microemacs) behaves as you describe ed 0.4 does,
except without the error message -- it just spins silently getting EIO
from reading stdin. i think em needs to be fixed, and it sounds like
GNU ed already has been. (unless i misunderstand the relationship of
0.4 and 1.6.)
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
paul fox, p...@foxharp.boston.ma.us (arlington, ma, where it's 57.2 degrees)
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html