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:11:21 +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: <20020422211121.B7762@cygbert.vinschen.de>
Mail-Followup-To: cygwin AT cygwin DOT com, vim-dev AT vim DOT org
References: <Pine DOT LNX DOT 4 DOT 44 DOT 0204221337140 DOT 19476-100000 AT rd DOT incert DOT com> <200204221835 DOT g3MIZoU02673 AT moolenaar DOT net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200204221835.g3MIZoU02673@moolenaar.net>
User-Agent: Mutt/1.3.22.1i

On Mon, Apr 22, 2002 at 08:35:50PM +0200, Bram Moolenaar wrote:
> I'm quite sure this is not a good solution.  It's just waiting to fail
> in another place.  The Unix code just isn't prepared for backslashes in
> a file name to be path separators, they are seen as escaping the special
> meaning of characters.
> 
> Why not add something at the start of main() to change backslashes to
> forward slashes?  Or better: Isn't there a cygwin trick for this
> already?

Sure: 

   #include <sys/cygwin.h>

   cygwin_conv_to_posix_path(const char *win_path, char *posix_path);

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/