Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive:	<http://sourceware.cygnus.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help:	<mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
Date:	Sun, 28 May 2000 12:14:33 -0400
From:	Chris Faylor <cgf AT cygnus DOT com>
To:	Earnie Boyd <earnie_boyd AT yahoo DOT com>
Cc:	cygwin users <cygwin AT sourceware DOT cygnus DOT com>
Subject:	Re: File name syntax (WAS: RE: FW: Can not config sshd)
Message-ID:	<20000528121433.A1363@cygnus.com>
Reply-To:	cygwin AT sourceware DOT cygnus DOT com
Mail-Followup-To:	Earnie Boyd <earnie_boyd AT yahoo DOT com>,
	cygwin users <cygwin AT sourceware DOT cygnus DOT com>
References:	<20000528151415 DOT 4262 DOT qmail AT web109 DOT yahoomail DOT com>
Mime-Version:	1.0
User-Agent:	Mutt/1.2i
In-Reply-To:	<20000528151415.4262.qmail@web109.yahoomail.com>; from earnie_boyd@yahoo.com on Sun, May 28, 2000 at 08:14:15AM -0700

On Sun, May 28, 2000 at 08:14:15AM -0700, Earnie Boyd wrote:
>--- Chris Faylor <cgf AT cygnus DOT com> wrote:
>-8<-
>> I have mixed feelings about this.  I routinely use //sys/share to access
>> remote
>> shares.  If cygwin had translated sys:share to //sys/share two or three years
>> ago then I would be using that mechanism instead.
>> 
>> Unfortunately, this use is embedded in various scripts on my machine.  I
>> would
>> be surprised if I was the only person who would be affected by this.
>
>Well, we've changed the way other things work without regard to what might
>break by doing so, e.g., the Windows path \ deal.  So, what's the sweat about
>this change, you just fix what breaks.

If you're referring to the use of backslash in path specs, the intent was to
help a lot of people who had a natural assumption that \foo\bar would refer
to c:\foo\bar if they were on the c: drive.  As you can see, I'm trying to
accomodate the Windows assumptions here.

Changing cygwin so that it ignored a leading // would be exactly the opposite
philosophy and it would basically just accomodate broken software rather
than natural user assumptions.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -