X-Spam-Check-By: sourceware.org Date: Wed, 20 Sep 2006 20:48:15 -0700 From: Christopher Layne To: cygwin AT cygwin DOT com Subject: Re: bash-3.1-7 BUG Message-ID: <20060921034815.GC6790@ns1.anodized.com> References: <20060913052510 DOT GB1256 AT trixie DOT casa DOT cgf DOT cx> <45089854 DOT 8010705 AT scytek DOT de> <20060914001902 DOT GB24899 AT trixie DOT casa DOT cgf DOT cx> <4508ABAF DOT 5090408 AT scytek DOT de> <20060914020737 DOT GC24899 AT trixie DOT casa DOT cgf DOT cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060914020737.GC24899@trixie.casa.cgf.cx> User-Agent: Mutt/1.5.11 X-Assp-Spam-Prob: 0.00000 X-Assp-Whitelisted: Yes X-Assp-Envelope-From: clayne AT ns1 DOT anodized DOT com X-Assp-Intended-For: cygwin AT cygwin DOT com X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: 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 > I suspect that the "Well, they can just install Linux (floppies, CDs, > DVDs) if they feel like it" observation has been made several times a > year for the last ten years. It's obviously not a very powerful > argument since Cygwin is still here and you can't really assert that the > only reason it is here is because make understood MS-DOS paths or bash > dealt properly with \r\n line endings. I personally use Cygwin to make full use of a unix shell and environ along side windows - typically with around 8-10 puttycygs open along with NX clients to Linux machines running NX. Since it's inevitable that windows will creep into things, there's not much one can do to get around it - aside from making a personal pact 'not going to use windows' - which we've all most likely done and eventually failed out. That being said, if I didn't require just a few windows applications that I use aside from Cygwin, I'd be running KDE/Linux 2.6 on this box in a heartbeat. That being said, I think cygwin is great, and I find it invaluable under windows. I really couldn't imagine using MSW without cygwin. > I doubt that Eric will want to deal with the fallout of having bash not > understand \r\n line endings but, if he does, it would be his decision > and, again, I would support it 100%. I am very eager to see things like > configure scripts work faster and if we have to drop a few scared or > lazy people along the way to accomplish that goal, that's fine with me. > I have no problem at all with being a part of a smaller community which > doesn't need to use notepad to edit their bash scripts. Yep - and what section of the bell curve do people who write in bash/sh *on* cygwin *also* use notepad to edit the files? I would think 95% are using vi/vim. -cl -- 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/