From: Chris Faylor <cgf@cygnus.com>
To: "cygwin@sourceware.cygnus.com" <cygwin@hotpop.com>
Subject: Re: File name syntax (WAS: RE: FW: Can not config sshd)
Date: Fri, 26 May 2000 14:42:00 -0000 [thread overview]
Message-ID: <20000526174136.C23535@cygnus.com> (raw)
In-Reply-To: <4.3.1.2.20000526171225.00e6e7e0@pop.ma.ultranet.com>
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 "//<server name>/<share name>" 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@sourceware.cygnus.com
next prev parent reply other threads:[~2000-05-26 14:42 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
2000-05-27 16:19 ` AJ Reins
2000-05-27 16:50 ` Chris Faylor
[not found] <200005301721.KAA00107@cygnus.com>
2000-05-30 10:35 ` Chris Faylor
2000-05-30 10:21 Parker, Ron
-- strict thread matches above, loose matches on Subject: below --
2000-05-29 6:14 Bernard Dautrevaux
2000-05-29 6:07 Bernard Dautrevaux
2000-05-28 8:14 Earnie Boyd
2000-05-28 9:14 ` Chris Faylor
2000-05-29 10:28 ` Andy Hare
2000-05-28 0:17 David Bolen
[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
[not found] <200005262150.OAA10858@cygnus.com>
2000-05-26 15:04 ` Chris Faylor
2000-05-27 16:27 ` AJ Reins
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
2000-05-26 14:27 Parker, Ron
2000-05-26 14:16 Parker, Ron
2000-05-26 14:10 Parker, Ron
[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 10:19 Earnie Boyd
[not found] <200005261701.NAA11863@acestes-fe0.ultra.net>
2000-05-26 10:10 ` Larry Hall (RFK Partners, Inc)
2000-05-26 10:01 Parker, Ron
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=20000526174136.C23535@cygnus.com \
--to=cgf@cygnus.com \
--cc=cygwin@hotpop.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).