From: Andreas Schwab <schwab@linux-m68k.org>
To: Kevin Ballard <kevin@sb.org>
Cc: Drew Northup <drew.northup@maine.edu>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Manual hunk edit mode + emacs + ^G == garbage
Date: Thu, 14 Oct 2010 00:40:34 +0200 [thread overview]
Message-ID: <m27hhld8d9.fsf@igel.home> (raw)
In-Reply-To: <24AC771D-07A7-49D7-8824-28E6156C90B4@sb.org> (Kevin Ballard's message of "Wed, 13 Oct 2010 14:53:05 -0700")
Kevin Ballard <kevin@sb.org> writes:
> I've been investigating this on the emacs side as well. At the moment, my suspicion is that ^G causes emacs to trigger (keyboard-quit), but at the same time the surrounding environment (e.g. git) is sending a SIGINT to emacs, which normally acts like ^G but in this case may be triggering the emergency exit mode of emacs. Is there some reason that the interactive add would be sending SIGINT to emacs when I type ^G?
If you are using text mode (-nw) then Emacs redefines the INTR character
of the terminal to ^G. On the other hand it should also put itself into
its own process group, so the parent should not receive the terminal
signals. And this is what happens here when I try it.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2010-10-13 22:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-13 21:37 Manual hunk edit mode + emacs + ^G == garbage Kevin Ballard
2010-10-13 21:48 ` Drew Northup
2010-10-13 21:53 ` Kevin Ballard
2010-10-13 22:40 ` Andreas Schwab [this message]
2010-10-13 22:49 ` Kevin Ballard
2010-10-14 9:37 ` Ævar Arnfjörð Bjarmason
2010-10-14 9:47 ` Kevin Ballard
2010-10-14 9:51 ` Miles Bader
2010-10-15 9:13 ` Kevin Ballard
2012-02-22 21:43 ` Matt McClure
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=m27hhld8d9.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=drew.northup@maine.edu \
--cc=git@vger.kernel.org \
--cc=kevin@sb.org \
/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).