Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Mon, 22 Jul 2002 11:03:44 +0400 From: egor duda Reply-To: egor duda Organization: deo X-Priority: 3 (Normal) Message-ID: <91341174502.20020722110344@logos-m.ru> To: "David A. Cobb" CC: cygwin@cygwin.com Subject: Re: Valid file-name characters In-Reply-To: <3D3999D5.2080904@cox.net> References: <3D3999D5.2080904@cox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi! Saturday, 20 July, 2002 David A. Cobb superbiskit@cox.net wrote: DAC> Back in May (where I'm still trying to catch up) there was a discussion DAC> starting at http://www.cygwin.com/ml/cygwin/2002-05/msg01041.html DAC> concerning a colon in a filename -- valid in *nix, not in Windows. DAC> Also, we get repeated griping about the encoding of URI's in the local DAC> package cache. DAC> Would you consider a patch that translated filenames containing special DAC> characters: the Cygwin user would see "aux:" but Windows would see DAC> "aux%??" (I don't recall the encoding of colon)? The only problem here is what to do if cygwin user wants to create both aux: and aux% Egor. mailto:deo@logos-m.ru ICQ 5165414 FidoNet 2:5020/496.19 -- 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/