X-Recipient: archive-cygwin@delorie.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 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@cygwin.com Subject: Re: Sending signals to a subprocess References: <4CB9DE15.8010308@cornell.edu> <4CBC3F43.9010602@cornell.edu> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.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