RE: find cmd and bash

[Kenneth Farley <KFarley at alidian dot com>]

Thanks. I tried single + double quotes. Same problem. I also looked at the
files and there are no spaces. In fact if you just -print everything is
fine.

						KCF

		-----Original Message-----
		From:	Earnie Boyd [mailto:earnie_boyd@yahoo.com]
		Sent:	Thursday, March 22, 2001 10:27 AM
		To:	Kenneth Farley
		Cc:	'cygwin@cygwin.com'
		Subject:	Re: find cmd and bash

		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