X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=3.7 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,KAM_THEBAT,RCVD_IN_BRBL_LASTEXT X-Spam-Check-By: sourceware.org Date: Wed, 13 Oct 2010 06:31:22 +0400 From: Andrey Repin Reply-To: Andrey Repin Message-ID: <385752694.20101013063122@mtu-net.ru> To: Autotoonz , cygwin@cygwin.com Subject: Re: nodosfilewarning not working In-Reply-To: <29948847.post@talk.nabble.com> References: <29948673.post@talk.nabble.com> <20101013011127.GA14097@ednor.casa.cgf.cx> <4CB5093E.4010103@tundraware.com> <29948847.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Greetings, Autotoonz! > Tim Daneliuk wrote: >> >> You can also permanently set this environment variable from Windows itself >> so >> that all instantiations of cygwin environments - regardless of shell will >> see it. >> > No I can't, as stated in the OP. No, you DIDN'T. It's rather clear from your posts, as you showed no diagnostics, only bare claims. > Also, this is no use for surpressing the warning when running individual > scripts Which (this your reply) convincing me even further that you don't have a clue in how environment variables works. -- WBR, Andrey Repin (anrdaemon@freemail.ru) 13.10.2010, <6:29> Sorry for my terrible english... -- 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