From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8566 invoked by alias); 13 Oct 2010 01:41:38 -0000 Received: (qmail 8557 invoked by uid 22791); 13 Oct 2010 01:41:29 -0000 X-Spam-Check-By: sourceware.org Received: from pool-98-110-186-10.bstnma.fios.verizon.net (HELO cgf.cx) (98.110.186.10) by sourceware.org (qpsmtpd/0.83/v0.83-20-g38e4449) with ESMTP; Wed, 13 Oct 2010 01:41:24 +0000 Received: from ednor.cgf.cx (ednor.casa.cgf.cx [192.168.187.5]) by cgf.cx (Postfix) with ESMTP id C415C13C061 for ; Tue, 12 Oct 2010 21:41:22 -0400 (EDT) Received: by ednor.cgf.cx (Postfix, from userid 201) id 908D52B352; Tue, 12 Oct 2010 21:41:22 -0400 (EDT) Date: Wed, 13 Oct 2010 01:41:00 -0000 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: nodosfilewarning not working Message-ID: <20101013014122.GA14285@ednor.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <29948673.post@talk.nabble.com> <20101013011127.GA14097@ednor.casa.cgf.cx> <29948823.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <29948823.post@talk.nabble.com> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2010-10/txt/msg00293.txt.bz2 On Tue, Oct 12, 2010 at 06:24:43PM -0700, Autotoonz wrote: >Christopher Faylor wrote: >>It's best to eschew the annoyance and conspiracy theories if you don't >>completely understand what's going on and actually want help. > >A fair comment, although I'm still puzzled as to how nobody can explain >why this fails You haven't provided the exact steps to show what doesn't work. This: >>On Tue, Oct 12, 2010 at 05:49:31PM -0700, Autotoonz wrote: >>>Here is the command line I'm running: C:\cygwin\bin\bash --login >>>C:\test\test.sh isn't much to go on. If you just type if from the CMD prompt you get the expected warning. What, precisely, did you do which you expected to work? You need to show the exact steps to reproduce the problem. >>c:\>set CYGWIN=nodosfilewarning >>c:\>C:\cygwin\bin\bash --login C:\test\test.sh >> >>You may need to create a .bat file if you want to just do the latter. > >As per my original post, this most definitely does *not* work. Have >you tried this yourself yet? Yes, I tried it. I tried it from the CMD prompt (which is where I tested this when I first implemented it) and I tried it from a .bat file. Both work as expected, i.e., no warning. cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple