git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: Johannes Sixt <j6t@kdbg.org>
Cc: "Trygve Aaberge" <trygveaa@gmail.com>,
	"Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>,
	git@vger.kernel.org
Subject: Re: Regression: Ctrl-c from the pager in an alias exits it
Date: Fri, 6 Jan 2017 18:20:43 -0500	[thread overview]
Message-ID: <20170106232042.ptn6grtll5wpxhc4@sigill.intra.peff.net> (raw)
In-Reply-To: <2ed6f78b-7704-c724-c99b-e310c383c4e8@kdbg.org>

On Fri, Jan 06, 2017 at 11:42:25PM +0100, Johannes Sixt wrote:

> > So I dunno. Maybe this waiting should be restricted only to certain
> > cases like executing git sub-commands.
> 
> If given it some thought.
> 
> In general, I think it is wrong to wait for child processes when a signal
> was received. After all, it is the purpose of a (deadly) signal to have the
> process go away. There may be programs that know it better, like less, but
> git should not attempt to know better in general.
> 
> We do apply some special behavior for certain cases like we do for the
> pager. And now the case with aliases is another special situation. The
> parent git process only delegates to the child, and as such it is reasonable
> that it binds its life time to the first child, which executes the expanded
> alias.

Yeah, I think I agree. That binding is something you want in many cases,
but not necessarily all. The original purpose of clean_on_exit was to
create a binding like that, but of course it can be (and with the
smudge-filter stuff, arguably has been) used for other cases, too.

I'll work up a patch that makes it a separate option, which should be
pretty easy.

-Peff

  reply	other threads:[~2017-01-06 23:20 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-05 14:25 Regression: Ctrl-c from the pager in an alias exits it Trygve Aaberge
2017-01-06  6:40 ` Jeff King
2017-01-06  6:47   ` Jeff King
2017-01-06  7:26     ` Jeff King
2017-01-06  7:32       ` Jeff King
2017-01-06 13:19         ` Trygve Aaberge
2017-01-06 14:39         ` Johannes Sixt
2017-01-06 19:41           ` Jeff King
2017-01-06 22:42             ` Johannes Sixt
2017-01-06 23:20               ` Jeff King [this message]
2017-01-07  1:14                 ` [PATCH 0/3] fix ^C killing pager when running alias Jeff King
2017-01-07  1:16                   ` [PATCH 1/3] execv_dashed_external: use child_process struct Jeff King
2017-01-07  1:17                   ` [PATCH 2/3] execv_dashed_external: stop exiting with negative code Jeff King
2017-01-07  1:22                   ` [PATCH 3/3] execv_dashed_external: wait for child on signal death Jeff King
2017-01-07  7:28                     ` Johannes Sixt
2017-01-07  7:34                       ` Jeff King
2017-01-07  9:07                     ` Duy Nguyen
2017-01-07 23:26                   ` [PATCH 0/3] fix ^C killing pager when running alias Jacob Keller
2017-01-07 23:27                     ` Jacob Keller

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170106232042.ptn6grtll5wpxhc4@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=j6t@kdbg.org \
    --cc=pclouds@gmail.com \
    --cc=trygveaa@gmail.com \
    /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 public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).