Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Message-ID:	<3D3999D5.2080904@cox.net>
Date:	Sat, 20 Jul 2002 13:11:49 -0400
From:	"David A. Cobb" <superbiskit AT cox DOT net>
Organization:	CoxNet User
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1b) Gecko/20020718
X-Accept-Language:	en-us, en
MIME-Version:	1.0
To:	Cygwin Discussion <cygwin AT cygwin DOT com>
Subject:	Valid file-name characters

Back in May (where I'm still trying to catch up) there was a discussion 
starting at http://www.cygwin.com/ml/cygwin/2002-05/msg01041.html 
concerning a colon in a filename -- valid in *nix, not in Windows.  

Also, we get repeated griping about the encoding of URI's in the local 
package cache.  

Would you consider a patch that translated filenames containing special 
characters: the Cygwin user would see "aux:" but Windows would see 
"aux%??" (I don't recall the encoding of colon)?

-- 
David A. Cobb, Software Engineer, Public Access Advocate
"By God's Grace I am a Christian man, by my actions a great sinner." -- The Way of a Pilgrim; R. M. French, tr.
Life is too short to tolerate crappy software.
.



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -