X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 	tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <2bf229d30902101011k15af32d8odc9ec470d71341a6@mail.gmail.com>
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> 	 <2bf229d30902100717p748855a2pfe3b9d6de33dbaba AT mail DOT gmail DOT com> 	 <20090210152949 DOT GU5416 AT calimero DOT vinschen DOT de> 	 <20090210164852 DOT GV5416 AT calimero DOT vinschen DOT de> 	 <2bf229d30902101011k15af32d8odc9ec470d71341a6 AT mail DOT gmail DOT com>
Date: Tue, 10 Feb 2009 21:39:53 -0500
Message-ID: <17393e3e0902101839t7405209ifcfd6d1940db117@mail.gmail.com>
Subject: Re: 1.7 - Odd behaviour with vim
From: Matt Wozniski <godlygeek AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Tue, Feb 10, 2009 at 1:11 PM, Chris Sutcliffe wrote:
>> On second thought, is it possible that you're using a native vim as well
>> and so maybe have a vim rc file with DOS paths in it?  Or an environment
>> variable containing a DOS path which is referred by both vims, as, say,
>> $VIM or $VIMRUNTIME?
>
> Yep, that was it, in one of my functions in .vimrc I was appending a
> '\tags' to the end, I now have added a 'if has("win32unix")' condition
> to append '/tags' to the string (I use a common .vimrc for both native
> and Cygwin vim).

Why not just append '/tags' to the string on both?  It will work fine
on both windows and cygwin (and linux, and dos, and mac os, etc).

> I don't recall seeing this behaviour in Cygwin
> 1.5.x, but never the less I'm all good now.

No, the warning is new with 1.7 to serve as a strong reminder that
using dos-style paths is unsupported and not guaranteed to work.

~Matt

--
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/