X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: <26363833.post@talk.nabble.com> References: <26363833 DOT post AT talk DOT nabble DOT com> Date: Sun, 15 Nov 2009 22:27:37 +0000 Message-ID: <416096c60911151427g12cc5582t6d9bbdc063c5b14a@mail.gmail.com> Subject: Re: Seems like treatment of NTFS ADS (foo:bar) changed between 1.5 and 1.7 but not mentioned in What's Changed From: Andy Koppe To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 2009/11/15 aputerguy: > In cygwin 1.7 > $ ls -1s foo* > 1 foo:bar > 1 foo:baz > > Which might seem ok, > *But* now explorer shows two files > foo[]bar > foo[]baz > where [] is a square box indicating an illegal symbol. The square box doesn't represent an illegal symbol but one that the font being used doesn't have a glyph for. To ensure POSIX filename transparency, Cygwin 1.7 maps characters that aren't allowed in Windows filenames to the Unicode private-use range at U+F000. So a colon is stored as U+F034. I'd suspect the support for ADSs in 1.5 was rather accidental anyway. POSIX programs certainly don't know about them, and you get the rather weird situation that "files" like foo:bar can be accessed but don't show up in the directory they're in. Hence I think the right way to access ADSs is via Windows tools. Unless there is a POSIXy way to represent them? Andy -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple