Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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: Thu, 13 Mar 2003 02:38:48 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Mixing / and \ path separators Message-ID: <20030313073848.GB26766@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <200303122208 DOT XAA17485 AT a0 DOT complang DOT tuwien DOT ac DOT at> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200303122208.XAA17485@a0.complang.tuwien.ac.at> User-Agent: Mutt/1.5.1i On Wed, Mar 12, 2003 at 11:08:27PM +0100, Anton Ertl wrote: >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? Cygwin "likes" paths with backslashes in them. It now just wisely assumes that such paths are windows paths. As I'm sure you know, you don't use '/' to denote a UNIX path. This is the way that it was supposed to work (for the last couple of years at least) but a bug crept in which caused things to stop functioning correctly. >If so, how should I deal with path names where parts of the path come >from ordinary windows users? Either tell your Windows users to use forward slashes, tell them to specify the path name using windows specs like f:\cygwin\foo\bar, or change the backslashes to slashes. cgf -- 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/