This is the mail archive of the
cygwin
mailing list for the Cygwin project.
RE: 1.5.25-7: problem about bash completion
- From: "Dave Korn" <dave dot korn at artimi dot com>
- To: <cygwin at cygwin dot com>
- Date: Wed, 9 Jan 2008 14:17:17 -0000
- Subject: RE: 1.5.25-7: problem about bash completion
- References: <ee03a2470712220143t782852a3w60fd8b9d8e51e4bc@mail.gmail.com> <20071222095758.GC29568@calimero.vinschen.de> <ee03a2470712222102pc7b85e9m9c4f308c0568bceb@mail.gmail.com> <20071223052601.GA23767@ednor.casa.cgf.cx> <ee03a2470712260907n429c5dc7q16b239206a29ce78@mail.gmail.com> <4784D349.1080703@byu.net>
On 09 January 2008 14:00, Eric Blake wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> According to kou yu on 12/26/2007 10:07 AM:
>>> POSIX *allows* '//something' to have a special meaning. It doesn't
>>> state that it is necessarily the syntax for SMB share paths.
>>>
>> In fact, if you simply say that this is not a bug of cygwin, but a
>> feature, then I would believe you.
>
> It is a feature of cygwin that // is used, in accordance with SUSv3 and
> POSIX, as the implementation-defined start for remote paths. It is a
> feature of Linux that // is treated as an implementation-defined synonym
> of /.
It's not just that: it's definitely a bug in applications when they blindly append paths without caring if they double up slashes or not, just because it /usually/ works.
cheers,
DaveK
--
Can't think of a witty .sigline today....
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/