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 Date: Tue, 8 Oct 2002 20:27:31 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: grep = * vs grep = * > foo Message-ID: <20021009002731.GA25291@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20021009002305 DOT 79648 DOT qmail AT web40514 DOT mail DOT yahoo DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021009002305.79648.qmail@web40514.mail.yahoo.com> User-Agent: Mutt/1.4i On Tue, Oct 08, 2002 at 05:23:05PM -0700, Sheryl McKeown wrote: >grepping and redircting the output to a file >causes a process loop that has to be killed > >17:17 0 [C:\Development\test] >.grep = * > delme > >17:18 66048 [C:\Development\test] >.^C > >What happens is that the grep starts reading the delme >file and then reporting all those finds... Right. The file is created before grep is started so when grep expands the '*' if finds delme and dutifully searches it... forever. >Ok, but the odd part this is, this behavior doesn't appear when using >the bash shell (on the same XP box). When run from the bash shell, bash itself first expands '*' and then creates delme. Since delme doesn't exist, it isn't searched. cgf -- Please do not send me personal email with cygwin questions. Use the resources at http://cygwin.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/