From: Jeff King <peff@peff.net>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>,
Paul Fox <pgf@foxharp.boston.ma.us>,
Krzysztof Mazur <krzysiek@podlesie.net>
Subject: [PATCH 5/5] launch_editor: propagate signals from editor to git
Date: Fri, 30 Nov 2012 17:41:50 -0500 [thread overview]
Message-ID: <20121130224149.GE23772@sigill.intra.peff.net> (raw)
In-Reply-To: <20121130223943.GA27120@sigill.intra.peff.net>
We block SIGINT and SIGQUIT while the editor runs so that
git is not killed accidentally by a stray "^C" meant for the
editor or its subprocesses. This works because most editors
ignore SIGINT.
However, some editor wrappers, like emacsclient, expect to
die due to ^C. We detect the signal death in the editor and
properly exit, but not before writing a useless error
message to stderr. Instead, let's notice when the editor was
killed by a terminal signal and just raise the signal on
ourselves. This skips the message and looks to our parent
like we received SIGINT ourselves.
The end effect is that if the user's editor ignores SIGINT,
we will, too. And if it does not, then we will behave as if
we did not ignore it. That should make all users happy.
Note that in the off chance that another part of git has
ignored SIGINT while calling launch_editor, we will still
properly detect and propagate the failed return code from
the editor (i.e., the worst case is that we generate the
useless error, not fail to notice the editor's death).
Signed-off-by: Jeff King <peff@peff.net>
---
editor.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/editor.c b/editor.c
index c892a81..065a7ab 100644
--- a/editor.c
+++ b/editor.c
@@ -39,7 +39,7 @@ int launch_editor(const char *path, struct strbuf *buffer, const char *const *en
if (strcmp(editor, ":")) {
const char *args[] = { editor, path, NULL };
struct child_process p;
- int ret;
+ int ret, sig;
memset(&p, 0, sizeof(p));
p.argv = args;
@@ -51,8 +51,11 @@ int launch_editor(const char *path, struct strbuf *buffer, const char *const *en
sigchain_push(SIGINT, SIG_IGN);
sigchain_push(SIGQUIT, SIG_IGN);
ret = finish_command(&p);
+ sig = ret + 128;
sigchain_pop(SIGINT);
sigchain_pop(SIGQUIT);
+ if (sig == SIGINT || sig == SIGQUIT)
+ raise(sig);
if (ret)
return error("There was a problem with the editor '%s'.",
editor);
--
1.8.0.1.620.g558b0aa
next prev parent reply other threads:[~2012-11-30 22:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-30 22:39 [PATCH 0/5] ignore SIG{INT,QUIT} when launching editor Jeff King
2012-11-30 22:40 ` [PATCH 1/5] run-command: drop silent_exec_failure arg from wait_or_whine Jeff King
2012-11-30 22:41 ` [PATCH 2/5] launch_editor: refactor to use start/finish_command Jeff King
2012-11-30 22:41 ` [PATCH 3/5] launch_editor: ignore terminal signals while editor has control Jeff King
2012-11-30 22:41 ` [PATCH 4/5] run-command: do not warn about child death from terminal Jeff King
2012-11-30 22:41 ` Jeff King [this message]
2012-12-01 12:34 ` [PATCH 0/5] ignore SIG{INT,QUIT} when launching editor Krzysztof Mazur
2012-12-01 15:48 ` Paul Fox
2012-12-02 10:04 ` Junio C Hamano
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=20121130224149.GE23772@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=krzysiek@podlesie.net \
--cc=pgf@foxharp.boston.ma.us \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).