Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com From: Chris Faylor Date: Wed, 24 May 2000 17:42:58 -0400 To: cygwin users Subject: Re: Changes in path handling in Cygwin-1.1.1 Message-ID: <20000524174258.A6174@cygnus.com> Reply-To: cygwin@sourceware.cygnus.com Mail-Followup-To: cygwin users References: <20000524213534.26759.qmail@web122.yahoomail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000524213534.26759.qmail@web122.yahoomail.com>; from earnie_boyd@yahoo.com on Wed, May 24, 2000 at 02:35:34PM -0700 On Wed, May 24, 2000 at 02:35:34PM -0700, Earnie Boyd wrote: >The following information may or may not cause you problems: > >Prior to cygwin-1.1.1 a path beginning with a \ was treated the same as >a path beginning with a /. As of cygwin-1.1.1 paths beginning with \ >are now considered absolute windows paths while paths beginning with / >are considered absolute cygwin paths. Also, a path containing but not >starting with a \ will be considered a relative windows path. I have >no idea what happens yet if there is a mix. If the path has a backslash it is considered a Windows path. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com