Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <43204ECA.3070204@lists.cichon.com> Date: Thu, 08 Sep 2005 16:46:34 +0200 From: Public Mailing Lists User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.11) Gecko/20050728 MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: xargs still nok? References: <20050908102658.GC5555@calimero.vinschen.de> <4320281B.6090005@lists.cichon.com> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes zzapper wrote: >Is Xargs still reqd for > >find . -name '*.cfm' -exec grep -i {} \; > > Well, not exatctly. grep -i does not show you the filename, if you call it this way. You could either use find . -name '*.cfm' -exec grep -i something {} /dev/null \; which would make grep to show the filename. grep will think that it searches multiple files, and will not find something in /dev/null. This solution works well under Unix. With Cygwin, you may not have devices available in /dev, depending on your installation. The solution with xargs is probably faster with a large number of files because the grep program is not started that often. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/