Mail Archives: cygwin/2001/09/14/15:22:25
Simon, DOS doesn't consider the semicolon to be a special character
(unlike bash, where it's a statement seperator). So by backslashing
that final semicolon, find doesn't see it. However, when I run the
command at a dos shell, I get:
/usr/bin/FIND: grep: No such file or directory
/usr/bin/FIND: grep: No such file or directory
/usr/bin/FIND: grep: No such file or directory
etc for each .c file. That's because when you run like this, you
haven't got all your fun cygwin environment set up. Since you're
giving an explicit path to find, I can tell that you don't have
cygwin\bin both. This means that when find runs, grep isn't on the
path. Try this:
f:\cygwin\bin\find . -name *.c -exec /usr/bin/grep -n -e blah {}
\dev\null ;
This got me the same results in my DOS shell as running
find . -name *.c -exec grep -n -e blash {} \;
did in my bash shell. Good luck-
Augustus
--Simon Heffer wrote:--
>HI,
>
>I'm trying to run this from EMACSNT and getting the missing argument
to
>-exec message...
>
>f:\cygwin\bin\find . -name *.c -exec grep -n -e blah {} \dev\null \;
>
>Any thoughts,
>
>Simon Heffer ( simon DOT heffer AT royalblue DOT com)
__________________________________________________
Terrorist Attacks on U.S. - How can you help?
Donate cash, emergency relief information
http://dailynews.yahoo.com/fc/US/Emergency_Information/
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -