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 Date: Tue, 3 Aug 2004 16:53:31 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Please help with 4NT and cygwin problem?? (WinXP) Message-ID: <20040803205331.GB24231@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20040803201806 DOT GA24082 AT trixie DOT casa DOT cgf DOT cx> <410FF67A DOT 2060108 AT comcast DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <410FF67A.2060108@comcast.net> User-Agent: Mutt/1.4.1i On Tue, Aug 03, 2004 at 04:32:58PM -0400, CyberZombie wrote: >OT: Any reason why you haven't moved to the Cygwin bash shell? IMO, >it's much better than 4NT (my prior command-line-of-choice prior to >Cygwin)... I don't agree. I love 4NT and use it + cygwin all of the time. I've used 4NT longer than I've used cygwin, in fact. Maybe I'm an unusual case because I update the cygwin DLL quite a bit and getting in and out of bash would be a pain, but I still think 4NT is great. cgf -- 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/