To: cygwin@cygwin.com
From: Oleksandr Gavenko <gavenko@bifit.com.ua>
Subject: Re: Sending signals to a subprocess
Date: Mon, 18 Oct 2010 16:12:26 +0300
Lines: 23
Message-ID: <i9hh3q$5sl$1@dough.gmane.org>
References: <4CB9DE15.8010308@cornell.edu> <i9h1gq$to1$1@dough.gmane.org> <4CBC3F43.9010602@cornell.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4
In-Reply-To: <4CBC3F43.9010602@cornell.edu>
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

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.)


--
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