X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <4B3B99F0.7060005@gmail.com> Date: Wed, 30 Dec 2009 18:20:32 +0000 From: Dave Korn User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Problem with wildcard from Windows References: <4B3B8786 DOT 9090506 AT cygwin DOT com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Thorsten Kampe wrote: > * Bengt Larsson (Wed, 30 Dec 2009 18:18:21 +0100) >>> 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 shell (Cmd) does the globbing. Describe your problem in a Microsoft > newsgroup. Hang on though, isn't there some code in the cygwin dll to do globbing for just this situation, when you want to launch a cygwin executable from a non-cygwin context? Perhaps that code has a problem with multi-byte chars or something; this could be a cygwin bug, couldn't it? cheers, DaveK -- 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