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
From:	Anton Ertl <anton AT a0 DOT complang DOT tuwien DOT ac DOT at>
Message-Id:	<200303122208.XAA17485@a0.complang.tuwien.ac.at>
Subject:	Mixing / and \ path separators
To:	cygwin AT cygwin DOT com
Date:	Wed, 12 Mar 2003 23:08:27 +0100 (MET)
Reply-To:	anton AT mips DOT complang DOT tuwien DOT ac DOT at
MIME-Version:	1.0

Cygwin 1.3.18(0.69/3/2) handles filenames like

/usr/local/share/gforth/0.5.9-20030201\kernl32l.fi

all right, where the "\" is meant as a path separator.  Cygwin
1.3.19(0.71/3/2) and 1.3.20 reportedly do not like such names (file
not found).  Is this intentional and will it stay that way?  If so,
how should I deal with path names where parts of the path come from
ordinary windows users?

Background: We use Cygwin for the Windows port of Gforth
(http://www.complang.tuwien.ac.at/forth/gforth/).  The Windows port
currently produces mixes like the above by default, and we could
change that; but I am worried about paths coming from the users (e.g.,
through the GFORTHPATH environment variable), which may use either
way.

- anton


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