Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Authentication-Warning: muppet23.cs.chalmers.se: koen owned process doing -bs Date: Thu, 7 Feb 2002 12:04:35 +0100 (MET) From: Koen Claessen To: Subject: Control-C in Windows command line programs Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Dear all, I have encountered the following problem, and I wonder if anyone has a good solution to it. I am running a number of programs that are compiled to be run in the Windows command shell (formerly called DOS command shell). I am running Windows 2000. It works fine to run them in cygwin bash as well. The only problem I have is that control-C does not behave as it should! Normally, in the Windows command shell, control-C is understood and handled by the applications themselves. But when I run them under cygwin, control-C terminates the application. I have tried to install traps, with no success. I have had this problem with virtually all applications installed on my computer which run in the windows command shell: Pine, Hugs, GHCi (the last two are interpreters for a programming language called Haskell), and sometimes even OpenSSH for cygwin has the same problem. I wonder if there is a general solution to this that somehow traps control-C and leaves my applications running. Thanks, /Koen. -- Koen Claessen http://www.cs.chalmers.se/~koen Chalmers University, Gothenburg, Sweden. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/