public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Parker, Ron" <rdparker@butlermfg.com>
To: cygwin <cygwin@sourceware.cygnus.com>
Subject: File name syntax (WAS: RE: FW: Can not config sshd)
Date: Fri, 26 May 2000 10:01:00 -0000	[thread overview]
Message-ID: <8341.959360495.0@NO-ID-FOUND.mhonarc.org> (raw)

> 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.

             reply	other threads:[~2000-05-26 10:01 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-26 10:01 Parker, Ron [this message]
     [not found] <200005261701.NAA11863@acestes-fe0.ultra.net>
2000-05-26 10:10 ` Larry Hall (RFK Partners, Inc)
2000-05-26 10:19 Earnie Boyd
     [not found] <200005261702.KAA22136@athena.veritas.com>
2000-05-26 10:21 ` Bob McGowan
2000-05-26 10:47   ` Larry Hall (RFK Partners, Inc)
2000-05-26 14:10 Parker, Ron
     [not found] <200005262110.RAA09230@acestes-fe0.ultra.net>
2000-05-26 14:15 ` Larry Hall (RFK Partners, Inc)
2000-05-26 14:42   ` Chris Faylor
2000-05-27 16:19     ` AJ Reins
2000-05-27 16:50       ` Chris Faylor
2000-05-26 14:16 Parker, Ron
2000-05-26 14:27 Parker, Ron
2000-05-26 14:51 Parker, Ron
2000-05-26 15:27 ` Bob McGowan
2000-05-26 16:00   ` Chris Faylor
2000-05-26 16:18     ` Bob McGowan
2000-05-26 16:49       ` Chris Faylor
2000-05-27  9:49         ` Larry Hall (RFK Partners, Inc)
2000-05-28  0:05         ` Robert McGowan
2000-05-28  3:51           ` Corinna Vinschen
     [not found] <200005262150.OAA10858@cygnus.com>
2000-05-26 15:04 ` Chris Faylor
2000-05-27 16:27   ` AJ Reins
     [not found] <200005262126.RAA23411@acestes-fe0.ultra.net>
2000-05-27  9:32 ` Larry Hall (RFK Partners, Inc)
2000-05-27  9:44   ` Chris Faylor
2000-05-27 10:15     ` Larry Hall (RFK Partners, Inc)
2000-05-27 17:07       ` Chris Faylor
2000-05-28  0:17 David Bolen
2000-05-28  8:14 Earnie Boyd
2000-05-28  9:14 ` Chris Faylor
2000-05-29 10:28   ` Andy Hare
2000-05-29  6:07 Bernard Dautrevaux
2000-05-29  6:14 Bernard Dautrevaux
2000-05-30 10:21 Parker, Ron
     [not found] <200005301721.KAA00107@cygnus.com>
2000-05-30 10:35 ` Chris Faylor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8341.959360495.0@NO-ID-FOUND.mhonarc.org \
    --to=rdparker@butlermfg.com \
    --cc=cygwin@sourceware.cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).