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 14:20:37 -0400 (EDT)
From:	Chris Metcalf <metcalf AT incert DOT com>
To:	Corinna Vinschen <cygwin AT cygwin DOT com>
cc:	cygwin AT cygwin DOT com
Subject:	Re: vim doesn't quite get backslash-separated paths right
In-Reply-To:	<20020422095017.A19421@cygbert.vinschen.de>
Message-ID:	<Pine.LNX.4.44.0204221409410.20331-100000@rd.incert.com>
MIME-Version:	1.0

On Mon, 22 Apr 2002, Corinna Vinschen wrote:
> Use the cygpath utility then.

This is awkward in the context of something like $EDITOR, which is spawned 
off by some non-Cygwin program to run vim.  In this case you'd either need 
to do a .bat file, or else a simple executable that ran cygpath and then 
exec'ed vim.  The vim fix turns out to be basically a one-liner anyway.

I've pretty well fixed up everything I need to now, and Cygwin is humming
along very nicely.  Many thanks to the efforts of all those involved.
(BTW, I've got a modified bash.exe that doesn't pass ":" to readlist as a
word-break character if anyone would like a patch or a binary.)

                Chris Metcalf -- InCert Software -- 1 (617) 621 8080
                metcalf AT incert DOT com -- http://www.incert.com/~metcalf


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

- Raw text -