Usage of Cygwin GNU grep missing files when using wild cards.

[Steven Bender]

Apparently the command grep -i PATN *.* will scan files and indicate special results for .EXE files,
and it will locate files of extension .BAT with the wildcard usage, but when I subset the search
by using grep -i PATN *.BAT to look for patn in just batch text files, it finds no matches.
By copying files (copy *.bat *.qqq) and making new copies, I can then use
grep -i PATN *.qqq and get the expected results.

It appears to treat the .BAT text file contents specially.
Is there a way around this ?




Steven Bender
***@yahoo.com

[John Cowan]

Post by Steven Bender
by using grep -i PATN *.BAT to look for patn in just batch text files,
it finds no matches.

I am not able to replicate this problem with grep 2.16.

If you mail me some of your .BAT files and tell me the pattern you are
looking for, I may be able to help. Don't mail them to the mailing list
at large, though.

[Eli Zaretskii]

Date: Thu, 25 Sep 2014 10:11:55 -0700
Apparently the command grep -i PATN *.* will scan files and indicate special results for .EXE files,
and it will locate files of extension .BAT with the wildcard usage, but when I subset the search
by using grep -i PATN *.BAT to look for patn in just batch text files, it finds no matches.
By copying files (copy *.bat *.qqq) and making new copies, I can then use
grep -i PATN *.qqq and get the expected results.

Could it be that the files are called *.bat (lowercase) and not *.BAT
(uppercase), and that the Cygwin grep is case-sensitive about file
names?

It appears to treat the .BAT text file contents specially.

I'd be very surprised if it did that.

[John Cowan]

Post by Eli Zaretskii
Could it be that the files are called *.bat (lowercase) and not *.BAT
(uppercase), and that the Cygwin grep is case-sensitive about file
names?

Cygwin is indeed case-sensitive about file names, though it's bash's
globbing that's involved here, not grep.