X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=1.7 required=5.0 tests=BAYES_50,FORGED_HOTMAIL_RCVD2,FREEMAIL_FROM,SPF_HELO_PASS,T_RP_MATCHES_RCVD,T_TO_NO_BRKTS_FREEMAIL,UNPARSEABLE_RELAY X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com connect(): No such file or directory From: Scott Wells Subject: Re: A workaround for CTRL-C not working on Windows console apps in ptys Date: Thu, 20 May 2010 23:31:59 +0000 (UTC) Lines: 16 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Scott Wells hotmail.com> writes: > Hi. I'm a longtime cygwin user (since it was gnu-win32) who has struggled to > solve one particular long-standing disconnect between cygwin and native Win32 > command-line utilities, notably that unless you're using a cygwin shell from a > cmd.exe window (or tools like Console2 that effectively co-opt the native > console), CTRL-C doesn't properly interrupt spawned native processes. Interesting...just on a whim I removed the alias/function for ant entirely and tried having it run the shell script instead of the batch file. That failed, but seemingly due to line endings. Then I used dos2unix to convert the ant shell script in-place and tried it and it worked, and lo and behold, it seems to properly handle CTRL-C as well. While ant isn't the only thing that drove me to try this workaround, it's definitely the main thing. I'll keep playing with this but, assuming it works as it seems to, this is great! -- 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