This is the mail archive of the
mailing list for the Cygwin project.
Re: Valid file-name characters
- From: egor duda <deo at logos-m dot ru>
- To: "Robert Collins" <robert dot collins at syncretize dot net>
- Cc: cygwin at cygwin dot com, "'David A. Cobb'" <superbiskit at cox dot net>
- Date: Mon, 22 Jul 2002 13:48:00 +0400
- Subject: Re: Valid file-name characters
- Organization: deo
- References: <000601c23161$55d02bd0$0200a8c0@lifelesswks>
- Reply-to: egor duda <cygwin at cygwin dot com>
Monday, 22 July, 2002 Robert Collins firstname.lastname@example.org wrote:
>> RC> I was just about to suggest that whatever character is used is used as
>> RC> an escape char rather than a literal replacement.
>> RC> i.e.
>> RC> WIN32 CYGWIN
>> 'aux%c' ->> 'aux:'
>> 'aux%%' ->> 'aux%'
>> which means that
>> touch $s
>> notepad $s
>> won't work.
RC> Unless cygwin detects that notepad is a non cygwin program, and therefor
RC> needs the on-disk name.
Even if cygwin knows that notepad is native program it can't tell for
sure if a%% is name of disk file. It may be a name of my dog to be
told from my computer speakers, for instance. An he surely won't like
if i misspell his name ;-)
'aux%' ->> 'aux:'
RC> touch $s
RC> notepad $s
RC> won't work either - unless cygwin detects that notepad...
That's exactly my point. Having some fancy rules for filename encoding
breaks interoperability with native tools. Escaping non-valid
characters like ':' is not big problem, since native tools can't use
such names anyway. But messing with valid characters like '%' is far
more dangerous and error-prone.
Egor. mailto:email@example.com ICQ 5165414 FidoNet 2:5020/496.19
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html