Read and respond to this message at: 
https://sourceforge.net/forum/message.php?msg_id=3134945
By: mdlueck

grep (GNU grep) 2.5.1

Maybe I am missing something, I am unable to get grep to recurse a directory
tree. See example...

================================
U:\Distrib\Win2K\Images>dir *.inf /b
hi.inf
ho.inf

U:\Distrib\Win2K\Images>dir FI600E\*.inf /b
SYSPREP.INF

U:\Distrib\Win2K\Images>head FI600E\SYSPREP.INF
;SetupMgrTag
[Unattended]
    OemSkipEula=Yes
    UnattendMode=FullUnattended
    DriverSigningPolicy=Ignore

U:\Distrib\Win2K\Images>grep -ir Oem *.inf

U:\Distrib\Win2K\Images>del *.inf

U:\Distrib\Win2K\Images>grep -ir Oem *.inf
grep: *.inf: Invalid argument
================================

It only found *.inf in the current directory, and if I remove those it further
compalins that no filespec matching files exist.

Also this grep seems to not like to have stdout piped to it for it to grep upon.

U:\Distrib\Win2K\Images>grep --help | grep -i version
grep: fstat: Invalid argument

Annoying beast! I'd like to move to this one since it is open source and more
current and standard, but this is a bit crazy in my opinion... need the simple
stuff to work! ;-)

On Linux with the same build of grep, the piping works fine, but the recurse
is also a pain there.

______________________________________________________________________
You are receiving this email because you elected to monitor this forum.
To stop monitoring this forum, login to SourceForge.net and visit: 
https://sourceforge.net/forum/unmonitor.php?forum_id=74807


-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
GnuWin32-Users mailing list
GnuWin32-Users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gnuwin32-users

Reply via email to