Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com X-Apparently-From: Message-ID: <3ABA19C7.A5E9EDC0@yahoo.com> Date: Thu, 22 Mar 2001 10:27:03 -0500 From: Earnie Boyd Reply-To: Earnie Boyd X-Mailer: Mozilla 4.76 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Kenneth Farley CC: "'cygwin@cygwin.com'" Subject: Re: find cmd and bash References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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