From: Jeff King <peff@peff.net>
To: Krzysztof Mazur <krzysiek@podlesie.net>
Cc: Paul Fox <pgf@foxharp.boston.ma.us>,
Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org
Subject: Re: Topics currently in the Stalled category
Date: Wed, 21 Nov 2012 14:34:02 -0500 [thread overview]
Message-ID: <20121121193401.GC16280@sigill.intra.peff.net> (raw)
In-Reply-To: <20121121092750.GA8262@shrek.podlesie.net>
On Wed, Nov 21, 2012 at 10:27:50AM +0100, Krzysztof Mazur wrote:
> > > * pf/editor-ignore-sigint (2012-11-11) 5 commits
> > >
> > > Avoid confusing cases where the user hits Ctrl-C while in the editor
> > > session, not realizing git will receive the signal. Since most editors
> > > will take over the terminal and will block SIGINT, this is not likely
> > > to confuse anyone.
> > >
> > > Some people raised issues with emacsclient, which are addressed by this
> > > re-roll. It should probably also handle SIGQUIT, and there were a
> > > handful of other review comments.
> > >
> > > Anybody interested in moving this forward?
> >
> > i started this, but then jeff took it and ran with it and made it
> > right. i think the remaining changes are small -- if jeff would
> > prefer, i can probably finish it. (but i won't guarantee not to
> > mess up the "From:" lines. :-)
> >
>
> I'm also interested. I sometimes use ":r !command" in vim, so far I never
> needed to use Ctrl-C, but maybe in future.
>
> The SIGINT part seems to be finished, we need to decide what about SIGQUIT.
My plan was to just add in SIGQUIT[1] alongside SIGINT (and I think
there may have been one or two other minor comments in response to the
series). I am on vacation this week, but can revisit it next week. If
somebody wants to re-roll it in the meantime, that would be fine with
me.
-Peff
[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.
next prev parent reply other threads:[~2012-11-21 19:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-21 2:46 Topics currently in the Stalled category Paul Fox
2012-11-21 9:27 ` Krzysztof Mazur
2012-11-21 19:34 ` Jeff King [this message]
2012-11-21 19:50 ` Paul Fox
2012-11-21 19:53 ` Junio C Hamano
2012-11-21 20:13 ` Jeff King
-- strict thread matches above, loose matches on Subject: below --
2012-11-19 23:55 What's cooking in git.git (Nov 2012, #06; Mon, 19) Junio C Hamano
2012-11-20 23:50 ` Junio C Hamano
2012-11-21 0:05 ` Topics currently in the Stalled category Junio C Hamano
2012-11-21 3:31 ` Felipe Contreras
2012-11-28 2:59 ` Jeff King
2012-11-28 3:10 ` Felipe Contreras
2012-11-28 3:12 ` Jeff King
2012-11-28 3:11 ` Jeff King
2012-11-28 3:15 ` Felipe Contreras
2012-11-28 3:22 ` Jeff King
2012-11-28 3:33 ` Felipe Contreras
2012-11-21 14:55 ` Marc Branchaud
2012-11-22 11:24 ` Nguyen Thai Ngoc Duy
2012-12-01 0:36 ` Adam Spiers
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=20121121193401.GC16280@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.
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).