Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: "Gary R. Van Sickle" To: "Cygwin Discussion" Subject: RE: Valid file-name characters Date: Sun, 21 Jul 2002 23:03:00 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-15" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal In-Reply-To: <3D3999D5.2080904@cox.net> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal > 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)? > This would allow mh and maildir mailboxes to work fully in mutt etc. As long as it would cause no problems with anything else, I don't see why not. -- Gary R. Van Sickle Brewer. Patriot. -- 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/