X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-1.2 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org From: Bengt Larsson To: cygwin@cygwin.com Subject: Re: Problem with wildcard from Windows Date: Wed, 30 Dec 2009 19:33:17 +0100 Message-ID: <217nj55lrltb7j4ht7esvbfhh7kj29df4e@4ax.com> References: <4B3B8786.9090506@cygwin.com> <4B3B9723.1000104@etr-usa.com> <4B3B9916.8070704@cygwin.com> <4B3B9B99.4080907@etr-usa.com> In-Reply-To: <4B3B9B99.4080907@etr-usa.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: 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 Warren Young wrote: >On 12/30/2009 11:16 AM, Larry Hall (Cygwin) wrote: >> On 12/30/2009 01:08 PM, Warren Young wrote: >>> Another thing that doesn't work: >>> >>> c:\> echo W* >> >> Ah, right. So my idea doesn't make sense. Never mind. ;-) > >I think we're looking at two bugs, though. The original post appears to >be about a Unicode or wide character issue. My example shows some kind >of weird discrimination: it works fine for ls.exe, but not echo.exe. It doesn't work for echo because "echo" is a builtin in the Windows shell. -- 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