X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
From: Andrew DeFaria <Andrew AT DeFaria DOT com>
Subject:  Re: Bash.exe stays open after Putty is closed
Date:  Sat, 05 Apr 2008 10:49:52 -0700
Lines: 35
Message-ID: <ft8e44$mf8$1@ger.gmane.org>
References:  <47F6B29F DOT 6020904 AT gmail DOT com> 	 <20080405093513 DOT GT5532 AT calimero DOT vinschen DOT de> 	 <b609cb3b0804050639k7de6a062s102b098d9f7e55db AT mail DOT gmail DOT com> 	 <ft8ao6$bjp$1 AT ger DOT gmane DOT org> 	 <b609cb3b0804050958r553d468do215278855f7df5fa AT mail DOT gmail DOT com> 	 <ft8bvu$fut$1 AT ger DOT gmane DOT org> <b609cb3b0804051037o390136adh411b2d6b6f48cfd5 AT mail DOT gmail DOT com>
Mime-Version:  1.0
Content-Type:  text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding:  7bit
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
In-Reply-To: <b609cb3b0804051037o390136adh411b2d6b6f48cfd5@mail.gmail.com>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

NightStrike wrote:
> Look, use whatever you want, I don't really care. If you like cygwin's 
> ssh, wonderful! I don't. Putty provides me the flexibility I need to 
> access many ssh features on a regular basis for the things that I do, 
> and is 3 clicks away from downloading/running on any system I use that 
> it's never touched before. cygwin ssh doesn't, and isn't. cygwin ssh 
> works great for you and gives you consistency accross many systems and 
> fits the requirements that you have for an ssh client. Different 
> strokes, different folks.
Use whatever you want too! Am I forcing you nor even insisting that you 
use rxvt instead? No. Geeze somebody's drunk too much coffee today eh?

Look, I was just discussing the issues, merits, benefits, likes and 
dislikes of such things. Other's can weigh the options and make their 
own decisions. Why do you take it the wrong way instead of just a 
friendly discussion of the differences? I think it's useful to have such 
technical debates. It brings out issues that others may be unaware of 
and may be helpful to them. If you do not wish to debate these then 
what's really kept you from simply not responding? Geeze, chill out 
dude! Life's too short!
> My intent on answering you was to show you that there are other 
> options out there. Because a person chooses to use putty or cygwin ssh 
> doesn't really matter. My question at the end, "Why NOT use it?" was 
> rhetorical to show that it's silly to expect that any one program is 
> going to be perfect for every single user, as was implied by your 
> question "Why use putty instead of ssh?"
>
> The takeaway is that if bash isn't handling a SIGHUP properly (As 
> Paul-Kenji pointed out), then that is an issue that can't be ignored 
> by saying "just use cygwin ssh".
You really need to stop being so damn defensive!
-- 
Andrew DeFaria <http://defaria.com>
Have you noticed since everyone has a camcorder these days no one talks 
about seeing UFOs like they used to?


--
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/