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 Date: Sun, 28 May 2000 12:14:33 -0400 From: Chris Faylor To: Earnie Boyd Cc: cygwin users Subject: Re: File name syntax (WAS: RE: FW: Can not config sshd) Message-ID: <20000528121433.A1363@cygnus.com> Reply-To: cygwin@sourceware.cygnus.com Mail-Followup-To: Earnie Boyd , cygwin users References: <20000528151415.4262.qmail@web109.yahoomail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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 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@sourceware.cygnus.com