Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Wed, 12 May 2004 17:43:32 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: bash: tab completion failure from (but not at) / Message-ID: <20040512154332.GO12030@cygbert.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20040512140835.GJ12030@cygbert.vinschen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i On May 12 16:17, Dave Korn wrote: > I reckon you could quote > http://www.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap04.html#tag_0 > 4_11 > to support the claim that what bash is doing is actually an invalid > transformation and should be considered a bug. That page says > > "A pathname consisting of a single slash shall resolve to the root directory > of the process. A null pathname shall not be successfully resolved. A > pathname that begins with two successive slashes may be interpreted in an > implementation-defined manner, although more than two leading slashes shall > be treated as a single slash." > > Therefore translating "/" to "//" has the effect of replacing an > unambiguous specs-defined interpretation with an implementation-defined > interpretation and is clearly invalid, even though it amounts to a null > tranformation on many *nix systems. Looking into the bash code, you'll see that this is a well-known fact to the bash developers. This bug just couldn't be easily uncovered, since it doesn't result in wrong behaviour on any system so far. Sheer luck that two bugs met each other :-) Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Co-Project Leader mailto:cygwin@cygwin.com Red Hat, Inc. -- 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/