X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: <20090210151332.GT5416@calimero.vinschen.de> References: <2bf229d30902100655j4e0550d3q3f830b7229a2160e AT mail DOT gmail DOT com> <20090210150322 DOT GS5416 AT calimero DOT vinschen DOT de> <2bf229d30902100705x3ec552c6p2114a2f42b3b5f48 AT mail DOT gmail DOT com> <20090210151332 DOT GT5416 AT calimero DOT vinschen DOT de> Date: Tue, 10 Feb 2009 10:17:38 -0500 Message-ID: <2bf229d30902100717p748855a2pfe3b9d6de33dbaba@mail.gmail.com> Subject: Re: 1.7 - Odd behaviour with vim From: Chris Sutcliffe To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: 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 > Uh, that explains it. The full message is > > MS-DOS style path detected: %s > Preferred POSIX equivalent is: %s > CYGWIN environment variable option "nodosfilewarning" turns off this warning. > Consult the user's guide for more details about POSIX paths: > http://cygwin.com/cygwin-ug-net/using.html#using-pathnames\n"); > > This message is only generated once per session and can be switched > off entirely using the CYGWIN=nodosfilewarning setting. > > Bottom line: Don't use DOS paths. Understood... I don't when within Cygwin shell. > Second bottom line: It would be interesting to learn why the message > has been printed, *iff* you didn't use a DOS path somewhere explicitely. In vim I'm executing: :e /cygdrive/c/source/emerge/trunk/Source/emergeLib/main.cpp Could it be related to using /cygdive? Chris -- Chris Sutcliffe http://emergedesktop.org -- 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/