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: "Parker, Ron" To: "Larry Hall (RFK Partners, Inc)" , "cygwin AT sourceware DOT cygnus DOT com" Subject: RE: File name syntax (WAS: RE: FW: Can not config sshd) Date: Fri, 26 May 2000 16:07:55 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: multipart/mixed; boundary="----_=_NextPart_000_01BFC756.C5E76C7A" Message-Id: <20000526211005.E90B5F805@mx1.hotpop.com> ------_=_NextPart_000_01BFC756.C5E76C7A Content-Type: text/plain; charset="windows-1252" > >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. ------_=_NextPart_000_01BFC756.C5E76C7A Content-Type: text/plain; charset=us-ascii -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com ------_=_NextPart_000_01BFC756.C5E76C7A--