Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Date: Mon, 22 Apr 2002 21:14:32 +0200
From: Corinna Vinschen <vinschen AT redhat DOT com>
To: cygwin AT cygwin DOT com
Cc: vim-dev AT vim DOT org
Subject: Re: small inter-operability patch for vim 6.1.2 for Cygwin
Message-ID: <20020422211432.C7762@cygbert.vinschen.de>
Mail-Followup-To: cygwin AT cygwin DOT com, vim-dev AT vim DOT org
References: <200204221835 DOT g3MIZoU02673 AT moolenaar DOT net> <Pine DOT LNX DOT 4 DOT 44 DOT 0204221439430 DOT 21178-100000 AT rd DOT incert DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0204221439430.21178-100000@rd.incert.com>
User-Agent: Mutt/1.3.22.1i

On Mon, Apr 22, 2002 at 03:08:07PM -0400, Chris Metcalf wrote:
> > Or better: Isn't there a cygwin trick for this already?
> 
> Well, "cygpath -u PATH" will convert a Windows path to a Unix path.  
> However, this means you can't just set $EDITOR to a simple executable,
> but have to walk it through a script (or dedicated binary) first.
> Also, it just seems wrong that vim doesn't handle a Windows path
> plausibly, when almost all of the other Cygwin tools do.

However, I don't see the problem in using `cygpath'.  It's designed
for that purpose.  I'm not quite sure if it makes sense to tweak
vim if there are already tools which do what you want.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin AT cygwin DOT com
Red Hat, Inc.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/