Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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
Date: Thu, 15 Jul 2004 06:48:36 +0200
From: Thorsten Haude <nedit AT thorstenhau DOT de>
To: cygwin AT cygwin DOT com
Subject: Re: UNC Pathname Handling within Applications
Message-ID: <20040715044836.GA12487@eumel.yoo.local>
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20040715033232 DOT GP25893 AT eumel DOT yoo DOT local> <20040715041527 DOT GB3427 AT trixie DOT casa DOT cgf DOT cx>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="rwEMma7ioTxnRzrJ"
Content-Disposition: inline
In-Reply-To: <20040715041527.GB3427@trixie.casa.cgf.cx>
X-Warning: Email may contain unsmilyfied humor and/or satire.
Keywords: Hardcore, but no child sex at all!
Organization: Central Services - We do the work, you do the pleasure.
User-Agent: Mutt/1.5.5.1i cd.edit_threads cd.trash_folder
X-IsSubscribed: yes

--rwEMma7ioTxnRzrJ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi,

* Christopher Faylor wrote (2004-07-15 06:15):
>On Thu, Jul 15, 2004 at 05:32:32AM +0200, Thorsten Haude wrote:
>>I know that NEdit is not the only application ignoring multiplied
>>slashes, so I wonder how this is normally handled with Cygwin. Indeed,
>>a simple test on Linux seems to indicate that fopen() accepts any
>>number of slashes, so this is not isolated to NEdit.
>
>Why would the fact that linux can open files with any number of slashes
>indicative of a problem with other applications?  Cygwin can open files
>with any number of slashes too as long as they are not the first slash.

I only wanted to point out that this might not be the first time that
this particular problem came up.


>>- The user guide ("Mapping path names") does tell me something about
>>what's to expect but little about implementation.
>
>Implementation of what?  It isn't obvious what you are expecting cygwin
>to do or how you are expecting it to help.  By the time Cygwin sees the
>file spec the extra slash has been removed.  There is no amount of help
>that cygwin can provide at that point.

Well, Cygwin does already provide services for converting filenames,
so I thought it might be worthwhile to ask whether similar services
exist for the point in question.


>>- Googling brought me zilch, all involved words seem to be much too
>>generic to find anything, and Google does not search for slashes.
>>- I was also looking for another document (Posix?) to help here but
>>came up empty.
>>
>>
>>My questions:
>>- Is there any standard way to approach this problem?
>
>This is an application problem, not a windows or cygwin problem.  Double
>slashes at the beginnning of a path name are allowed to mean something
>different and if an application doesn't recognize that fact, that is at
>least arguably a bug.

Where is it defined that double slashes at the beginning of a path are
allowed to mean something? Is this C? Posix? To find the source of
this convention could really help to find the best way to remove this
problem.


Thanks!


Thorsten
--=20
Rarely do we find people who willingly engage in hard, solid thinking.
There is an almost universal quest for easy answers and half-baked
solutions. Nothing pains some people more than having to think.
    - Martin Luther King

--rwEMma7ioTxnRzrJ
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFA9gykW/x2JEBlodoRAovYAKD7+ws+XRuFhnpGpQ3x3PGPkgdtjQCg2TsF
m07mvBEOSbGsLp+Aso1ReMM=
=8xSh
-----END PGP SIGNATURE-----

--rwEMma7ioTxnRzrJ--