"Bill Baxter" wrote > On Sat, Oct 25, 2008 at 1:40 PM, Steven Schveighoffer > <[EMAIL PROTECTED]> wrote: >> "Benji Smith" wrote >>> Bill Baxter wrote: >>>> Benji Smith wrote: >>>>> The key is to never never never use the cygwin shell. It's a piece of >>>>> garbage. But using the executables from the "cygwin\bin" directory >>>>> within >>>>> the windows shell... Priceless! >>>> >>>> Oh, I didn't realize that. There is one thing that doesn't work, >>>> which is probably what gave me the impression it was broken -- Windows >>>> paths with wildcards don't work. Like "grep c:\Windows\*.txt". But >>>> you're right that it does seem to work for both windows paths, and >>>> local wildcards, just not Windows paths with wildcards. >> >> It's not the paths with wildcards that is the problem. In this case, it >> is >> the shell. Grep is expecting the shell to expand the wildcards, as it >> does >> on unix. > > Read again. Particularly this part: > > "it does seem to work for both windows paths, **and local wildcards**, > just not Windows paths with wildcards". > (emphasis added) > > "grep Foo *.txt" works just fine. "grep Foo c:\*.txt" does not.
Then that must be something grep is doing extra. Or perhaps the Windows console selectively expands wildcards? I have no idea. It seems weird that grep would expand only current-directory wildcards (try grep Foo *, and see if it works. Windows normally only expands *.* to mean 'all files'). But in the case of using a cygwin shell, the shell expands all wildcards before passing arguments to grep. That much I do know. I haven't really had a need to use the windows shell in a long time ;) -Steve
