Message-Id: <200005261702.NAA03016@delorie.com> 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: cygwin Subject: File name syntax (WAS: RE: FW: Can not config sshd) Date: Fri, 26 May 2000 12:00:51 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: multipart/mixed; boundary="----_=_NextPart_000_01BFC733.F805186A" ------_=_NextPart_000_01BFC733.F805186A Content-Type: text/plain; charset="windows-1252" > No, bash defaults HOME to / and then that get's prepended to > the path name > after it resolves the tilde character ~ sor ~/myfile bcomes > //myfile. Now the > problem with //myfile is that // is translated to \\ and > \\myfile as a server > doesn't exist. The time it takes to eventually time out is > directly related to > the number of domains your associated with * the timeout > period * the number of > retries. This is the reason we now have /cygdrive instead of > using // to > denote an unmounted device/directory. Which makes me wonder would a patch to cygwin be welcome that did the following? * Make multiple introductory slashes on a path behave as a single introductory slash * Make paths that begin with name: and contain no backslashes behave as a network path 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. ------_=_NextPart_000_01BFC733.F805186A 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_01BFC733.F805186A--