X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-2.2 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Message-ID: <4B3B9723.1000104@etr-usa.com> Date: Wed, 30 Dec 2009 11:08:35 -0700 From: Warren Young User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.5) Gecko/20091204 Thunderbird/3.0 MIME-Version: 1.0 To: Cygwin-L Subject: Re: Problem with wildcard from Windows References: <4B3B8786.9090506@cygwin.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed 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 On 12/30/2009 10:18 AM, Bengt Larsson wrote: >> Try "noglob" if your shell is not Cygwin-aware. > > Eh? The problem is that it doesn't glob when it should. The shell is > standard CMD.EXE, ie Windows console. The behavior you're relying on is a nonstandard Cygwin extension which most Cygwin users, I dare say, don't even use themselves. It's an emulation of a feature all POSIX shells have, internal globbing. cmd.exe doesn't provide globbing services to programs it runs, so Cygwin by default ("CYGWIN=glob") tries to do this for you, but it appears there are weaknesses. Another thing that doesn't work: c:\> echo W* This should give "Windows" at least. What I'm having trouble understanding is why you've installed Cygwin but then insist on sticking with the primitive cmd.exe shell. Your globbing problem will go away if you switch to one of the many shells in the Cygwin package repository. -- 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