Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com From: Chris Faylor Date: Fri, 26 May 2000 17:41:36 -0400 To: "cygwin AT sourceware DOT cygnus DOT com" Subject: Re: File name syntax (WAS: RE: FW: Can not config sshd) Message-ID: <20000526174136.C23535@cygnus.com> Mail-Followup-To: "cygwin AT sourceware DOT cygnus DOT com" References: <200005262110 DOT RAA09230 AT acestes-fe0 DOT ultra DOT net> <4 DOT 3 DOT 1 DOT 2 DOT 20000526171225 DOT 00e6e7e0 AT pop DOT ma DOT ultranet DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <4.3.1.2.20000526171225.00e6e7e0@pop.ma.ultranet.com>; from lhall@rfk.com on Fri, May 26, 2000 at 05:13:34PM -0500 On Fri, May 26, 2000 at 05:13:34PM -0500, Larry Hall (RFK Partners, Inc) wrote: >At 04:07 PM 5/26/00, Parker, Ron wrote: >> > >In other words, "///myfile" would translate to "/myfile" and >> > >"machine:dir/file" or "machine:/dir/file" would map to the >> > Windows path >> > >\\machine\dir\file. >> >> > I'm assuming by "Make multiple introductory slashes", you're >> > excluding the >> > case of "//"? >> >>That wasn't exactly what I was thinking. I used three for emphasis, but >>meant that one or more initial slashes would be treated as a single initial >>slash. >> >>It is the Friday before a long weekend and I might be completely brain-dead, >>but I don't remember a special significance to '//' in UNIX. > >Right. The significance is for UNC paths which can be easily access currently >using "///" in Cygwin now... 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. Bash's use of // should be fixed, IMO. I did fix it once myself but I never forwarded the changes to the maintainer. My bad. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com