This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: find cmd and bash
- To: Kenneth Farley <KFarley at alidian dot com>
- Subject: Re: find cmd and bash
- From: Earnie Boyd <earnie_boyd at yahoo dot com>
- Date: Thu, 22 Mar 2001 10:27:03 -0500
- CC: "'cygwin at cygwin dot com'" <cygwin at cygwin dot com>
- References: <ED298BF0B6CED211956D0090273F7553FA7CE3@TNIDC1>
- Reply-To: Earnie Boyd <cygwin at cygwin dot com>
Kenneth Farley wrote:
>
> Sirs:
> I am trying to get two command sets to work using find. I have
> resolved getting the correct find in the path, but am still having problems.
>
> $ find . -type f -name *.cpp -print | xargs grep -n 'Xpif*'
>
> xargs: grep: No such file or directory
>
> find . \( -name '*.[ch]' -o -name '*.cpp' \) -exec ctags -u {} \;
>
> find: ctags: No such file or directory
> find: ctags: No such file or directory
> find: ctags: No such file or directory
> find: ctags: No such file or directory
> find: ctags: No such file or directory
> find: ctags: No such file or directory
> find: ctags: No such file or directory
> find: ctags: No such file or directory
> find: ctags: No such file or directory
> find: ctags: No such file or directory
>
> It seems to be the same type of problem in both cases. Which is passing the
> stuff from find to the next command.
>
Add quotes around the {} part of the command. My guess is you have
files with spaces in the name.
Earnie.
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple