Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Originating-IP: [129.78.64.17] From: "Gareth Pearce" To: cygwin AT cygwin DOT com Subject: Re: grep -i -R path32 * vs grep -i -R path32 *.vb* Date: Thu, 10 Oct 2002 00:18:52 +0000 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 10 Oct 2002 00:18:53.0283 (UTC) FILETIME=[9D5F4330:01C26FF2] >Ok, I can live with that. For my understanding, what >does the -R expand then? I had visualized that -R >with grep was simular to ls -R. Where ls -R magically >displays all files with out having to specify a search >path. So I was thinking that grep -R magically >searched all the files without having to specify a >search path, and the *.vb* was the file designation. ls -R works identically as grep -R ... the ls command merely 'defaults' to . if no file is given - where as grep defaults to 'stdin' . try ls -R *.vb* - you will see it gives you nothing as well. > >However, the conclusion I'm coming to is that the >[FILE] of "Usage: grep [OPTION]... PATTERN [FILE] ..." >is really a directory _and_ file pattern. -R means 'recurse any directories in the input set.' when the input set is *.vb* - theres no directories - so no recursion occurs. Gareth - idly ponders why the grep he installed himself on this dec machine doesnt have --include. _________________________________________________________________ Chat with friends online, try MSN Messenger: http://messenger.msn.com -- 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/