X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=0.7 required=5.0 tests=AWL,BAYES_50,SPF_NEUTRAL,T_RP_MATCHES_RCVD
X-Spam-Check-By:	sourceware.org
Message-ID:	<4CBC4977.30600@cornell.edu>
Date:	Mon, 18 Oct 2010 09:19:51 -0400
From:	Ken Brown <kbrown AT cornell DOT edu>
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: Sending signals to a subprocess
References:	<4CB9DE15 DOT 8010308 AT cornell DOT edu> <i9h1gq$to1$1 AT dough DOT gmane DOT org> <4CBC3F43 DOT 9010602 AT cornell DOT edu> <i9hh3q$5sl$1 AT dough DOT gmane DOT org>
In-Reply-To:	<i9hh3q$5sl$1@dough.gmane.org>
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

On 10/18/2010 9:12 AM, Oleksandr Gavenko wrote:
> On 18.10.2010 15:36, Ken Brown wrote:
>> On 10/18/2010 4:46 AM, Oleksandr Gavenko wrote:
>>> On 16.10.2010 20:17, Ken Brown wrote:
>>>> I could use some help fixing a longstanding bug in the Cygwin build of
>>>> emacs, in which emacs is unable to send signals to subprocesses.
>>>
>>> This off top but I use native Emacs and have annoying bug:
>>>
>>> in C-x shell if I start cygwin app it can not be broken by C-c C-c (try
>>> run 'yes' utility).
>>
>> Yes, this is a known problem with native emacs and is documented in
>> etc/PROBLEMS. But Cygwin emacs will no longer have this problem as of
>> Emacs 23.3.
> Did you mean
>
> ** Interrupting Cygwin port of Bash from Emacs doesn't work.
>
> Cygwin 1.x builds of the ported Bash cannot be interrupted from the
> MS-Windows version of Emacs.  This is due to some change in the Bash
> port or in the Cygwin library which apparently make Bash ignore the
> keyboard interrupt event sent by Emacs to Bash.  (Older Cygwin ports
> of Bash, up to b20.1, did receive SIGINT from Emacs.)

Yes.  But let's not discuss native emacs further.  It's off topic for 
the cygwin list and also for this thread.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -