Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
From: "Andrew G. Tereschenko" <tag AT ibis DOT odessa DOT ua>
To: "Cygwin Users List" <cygwin AT cygwin DOT com>
Subject: Special chars inside filename
Date: Mon, 5 Feb 2001 16:36:34 +0200
Message-ID: <OCECJNJHOHFDNOOHJFIHOEDOFBAA.tag@ibis.odessa.ua>
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2410.0000
X-Return-Path: tag AT ibis DOT odessa DOT ua
X-MDaemon-Deliver-To: cygwin AT cygwin DOT com
Reply-To: tag AT ibis DOT odessa DOT ua

Hi,

I. Is there any environment option/proposed patch
to support special as for Win32) chars inside POSIX filenames ?

Win32 reserved for use this set of symbols:
< > : " / \ |
As result not all filenames allowed in Cygwin twitch allowed
in real *nix.

Currently I'm unable to decompress news archive for a leafnode
because of filenames like "<OAlNo66RAHA DOT 444 AT CPMSBNEWSW02 DOT betanews DOT com>"
(without double quotes). This archive was assembled under Solaris and
this filenames was valid...

Will it be Ok if Cygwin will encode this chars in valid char sequence ?

II. Is it possible to change \ behavior ??
Example:
1. bash-2.04$ uname -a
CYGWIN_NT-5.1 TAG 1.1.2(0.21/3/2) 2000-06-06 22:20 i686 unknown
bash-2.04$ cat > c\\a
bash: c\a: No such file or directory

2. [tag AT tigger2 ~]$ uname -a
SunOS tigger2 5.7 Generic_106542-02 i86pc i386 i86pc
[tag AT tigger2 ~]$ cat > c\\a
 ^D
[tag AT tigger2 ~]$ ls -la c*
-rw-r--r--   1 tag      tag            1 Feb  5 09:04 c\a

I think if Cygwin will encode all possible *nix filenames
into restricted set of win32 filenames then it will be easy
to add unicode/localised filenames support.
Also i think that we must strictly define which
filenames are POSIX and which Win32.

So ? What do think about this ?

=============================
Andrew G. Tereschenko
Software Engineer
Integrated Banking Information Systems
tag AT ibis DOT odessa DOT ua



--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple