X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
From: "Dave Korn" <dave DOT korn AT artimi DOT com>
To: <cygwin AT cygwin DOT com>
References: <ee03a2470712220143t782852a3w60fd8b9d8e51e4bc AT mail DOT gmail DOT com> 	 <20071222095758 DOT GC29568 AT calimero DOT vinschen DOT de> 	 <ee03a2470712222102pc7b85e9m9c4f308c0568bceb AT mail DOT gmail DOT com> 	 <20071223052601 DOT GA23767 AT ednor DOT casa DOT cgf DOT cx> <ee03a2470712260907n429c5dc7q16b239206a29ce78 AT mail DOT gmail DOT com> <4784D349 DOT 1080703 AT byu DOT net>
Subject: RE: 1.5.25-7: problem about bash completion
Date: Wed, 9 Jan 2008 14:17:17 -0000
Message-ID: <00e201c852ca$58377500$2e08a8c0@CAM.ARTIMI.COM>
MIME-Version: 1.0
Content-Type: text/plain; 	charset="UTF-8"
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <4784D349.1080703@byu.net>
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id m09EHhES005266

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/