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:	Fri, 16 Jul 2004 22:00:39 +0200
From:	Thorsten Haude <nedit AT thorstenhau DOT de>
To:	cygwin AT cygwin DOT com
Subject:	Re: UNC Pathname Handling within Applications
Message-ID:	<20040716200039.GD14685@eumel.yoo.local>
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<20040715033232 DOT GP25893 AT eumel DOT yoo DOT local> <cd71s1$rbd$1 AT sea DOT gmane DOT org> <20040715233034 DOT GA3729 AT eumel DOT yoo DOT local> <cd976s$kjr$1 AT sea DOT gmane DOT org>
Mime-Version:	1.0
In-Reply-To:	<cd976s$kjr$1@sea.gmane.org>
X-Warning:	Email may contain unsmilyfied humor and/or satire.
Keywords:	In Israel war der Saddam =?iso-8859-1?Q?Hu?= =?iso-8859-1?Q?ssein_noch_nie=2C_h=F6chstens?= im Geheimen.
Organization:	Ministry of Information, Department of Records
User-Agent:	Mutt/1.5.5.1i cd.edit_threads cd.trash_folder
X-IsSubscribed:	yes

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

Hi,

* Shankar Unni wrote (2004-07-16 20:36):
>Thorsten Haude wrote:
>
>>The path is also displayed at various places. The user might be
>>surprised to see surplus slashes.
>
>[Starting to drift OT, sorry..]
>
>Who's generating the surplus slashes? Is this because of trailing "/" in=
=20
>paths, and you're internally compositing names somehow?

Yes, we never cared for that because we weren't aware of this leading
slash thing. (I wasn't at least, and never heard about it before.) So
we have to check all internals for problems.

There will probably also be problems with the toolkit.


>I thought the only names you would *show* to the user would be the names=
=20
>of editor buffers, etc., something which the user has already specified=20
>explicitly anyway. It's not like you're saying "nedit myfile", and=20
>you're searching all over the filesystem to locate myfile..

The filename is used in several parts of the application. I expect
some of them to make false assumptions about leading slashes.


>I.e. if you're doing "prefix + basename", then the only normalization=20
>should be between prefix and basename (i.e. strip trailing slashes (any=20
>kind) from prefix, and append a "known slash" and basename).
>
>You shouldn't be doing any further normalization (e.g. /x/../y -> /y or=20
>any such), because if it *is* a synthesized name, then there's great=20
>value in knowing *how* the name was synthesized. Normalizing it loses=20
>this information.

These are the things we have to think about, yes.


Thorsten
--=20
Getting a thrill out of some stupid quote is a sign of idiocy.
    - turmeric

--8w3uRX/HFJGApMzv
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFA+DPnW/x2JEBlodoRAglrAKCRUBfFG+qwmcQDBn8manT8zDu28ACg9XHP
ig/qkLgyne8KLqjWoo4Yo5I=
=lbJP
-----END PGP SIGNATURE-----

--8w3uRX/HFJGApMzv--

- Raw text -