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 Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <3D4F86C6.8080109@onevision.de> Date: Tue, 06 Aug 2002 10:20:22 +0200 From: Roland Schwingel Organization: OneVision Software AG User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.0) Gecko/20020530 X-Accept-Language: de, de-de, en-us, en MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: RXVT and CTRL-C Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Hi... Long time I used the bash running thru CMD.exe. A few days ago I switched to rxvt. Really nice. Fast and much more comfortable. BUT, I recently encountered a problem... Hitting CTRL-C is not working everywhere. A find -type f -print can be canceled easily. But my self programmed stuff can no longer be breaked with CTRL-C. (everything is compiled to run in mingwin). I have to kill it with Taskmanager. Installed Packages (only the ones I think they are interesting for the case to save bandwidth) bash 2.05b-2 cygwin 1.3.12-4 (or 1.3.10-1) mingw-runtime 1.3-2 rxvt 2.7.2-10 When I am working with CMD.exe instead of rxvt everything is fine... But I don't want to use CMD.exe any more... When running with CMD.exe TERM=cygwin when running rxvt TERM=xterm. But doing a export TERM=cygwin in rxvt does not solve the problem... Anything known about this (couldn't find anything suitable in the archive)? Thanks, Roland -- 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/