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: Daniel Miller Subject: Re: Please help with 4NT and cygwin problem?? (WinXP) Date: Tue, 3 Aug 2004 21:33:28 +0000 (UTC) Organization: Cathartes Aura Lines: 19 Message-ID: References: <20040803201806 DOT GA24082 AT trixie DOT casa DOT cgf DOT cx> <410FF67A DOT 2060108 AT comcast DOT net> X-Complaints-To: usenet AT sea DOT gmane DOT org X-Gmane-NNTP-Posting-Host: adsl-68-123-123-20.dsl.snfc21.pacbell.net User-Agent: Xnews/06.08.25 X-IsSubscribed: yes CyberZombie wrote in news:410FF67A DOT 2060108 AT comcast DOT net: > 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)... > No, I find 4NT to be more flexible than BASH... filename completion is handier, especially when multiple filenames match what you type; editing of environment variables (especially PATH) with eset is unmatched by Bash, and there are some other handy things in 4NT as well, which are lacked by Bash. I do alot of work with Bash on my job, under Linux, and I often rue the absence of 4NT there... ... of course, that's when it works... Dan -- 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/