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 05:32:32 +0200
From:	Thorsten Haude <nedit AT thorstenhau DOT de>
To:	Cygwin ML <cygwin AT cygwin DOT com>
Subject:	UNC Pathname Handling within Applications
Message-ID:	<20040715033232.GP25893@eumel.yoo.local>
Mime-Version:	1.0
X-Warning:	Email may contain unsmilyfied humor and/or satire.
Keywords:	Haschisch, Marihuana, Kokain, Heroin, LSD und Extacy sind alles Drogen
Organization:	Ministry of Information, Department of Information Adjustments
User-Agent:	Mutt/1.5.5.1i cd.edit_threads cd.trash_folder
X-IsSubscribed:	yes

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

Hi,

I'm trying to find the best approach to solve a bug reported against
NEdit:=20
https://sourceforge.net/tracker/index.php?func=3Ddetail&aid=3D873188&group_=
id=3D11005&atid=3D111005

The reporter complains that NEdit cannot open files from network
shares using Cygwin's double-slash notation. That is not suprising,
since NEdit silently drops any doubled slash before using the path.


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.

- The user guide ("Mapping path names") does tell me something about
what's to expect but little about implementation.
- 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? Has it come up
before in other applications?
- Do you know a resource which explains how Posix apps are expected to
handle paths like this?
- Does Cygwin offer another way around this problem? Could cygpath be
of any help?


Thank you very much for any pointers you can give me!


Thorsten
--=20
Auch Hunger ist Krieg.
    - Willy Brandt

--v7CWsE/Dy737oYst
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFA9frQW/x2JEBlodoRAhaHAJ4zXN8YR8BN6wvv/alPAJLKxHfiagCgp6it
r8b+kPvSzLBgEBvGtFDPWRs=
=9GtS
-----END PGP SIGNATURE-----

--v7CWsE/Dy737oYst--

- Raw text -