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 To: cygwin AT cygwin DOT com From: Robert R Schneck Subject: Re: HELP: How to disable killing of Bash Shell window with mouse? Date: Tue, 14 Sep 2004 14:27:19 +0000 (UTC) Lines: 17 Message-ID: References: <1qoebilxzdy1c$.dlg AT thorstenkampe DOT de> <4146B06A DOT 4080706 AT x-ray DOT at> X-Complaints-To: usenet AT sea DOT gmane DOT org X-Gmane-NNTP-Posting-Host: 206-15-137-2.dialup.ziplink.net User-Agent: slrn/0.9.8.0 (CYGWIN_NT-5.1) X-IsSubscribed: yes Reini Urban wrote: > Thorsten Kampe schrieb: >> * Pekka Niiranen (2004-09-13 18:19 +0200) >>>Killing Cygwin Shell Window with mouse leaves bash.exe running. >> >> Recompile what? Cmd exe? Bash is a shell and knows nothing about the >> Windows Console "X" button. > > So, shouldn't the KILL message be propagated to its child process? > bash could react then. Or is it only propagated if bash would register > itself as an (invisible) window, just to receive those parent messages? Someone else will have to tell you whether that's possible for cmd.exe. But consider using rxvt instead, which is generally superior as long as you aren't using lots of Windows-native command-line tools. Robert -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/