X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Message-ID: Date: Wed, 14 May 2008 20:40:25 -0400 From: "Mark J. Reed" To: cygwin AT cygwin DOT com Subject: Re: grep raises signal ERR In-Reply-To: <20080515003601.GA18386@panix.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080515003601 DOT GA18386 AT panix DOT com> X-Google-Sender-Auth: dbba9ced0ea67ee9 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 You seem to be confused. ERR is not a signal; it is a shell feature designed to trap exactly the circumstance you're seeing: some command exits with nonzero status. A nonzero exit status is an "error", which is what ERR traps. What do you *want* the "aborting" message to mean? On 5/14/08, David Arnstein wrote: > Is this a bug? The following three-line shell script prints out the > string > > when executed. > > #!/bin/bash > trap "echo '' ; exit 1" ERR > grep -q -e 'foo' < /dev/null > > This indicates that grep has raised the signal ERR. It is inconvenient > for me. I am attempting to clean up some scratch files whenever a > shell script aborts. I use the trap command to do this. However, the > above command > grep -q -e 'foo' < /dev/null > is NOT aborting my shell script. It simply returns status 1, which I > do NOT want to handle by calling exit. > > -- > 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/ > > -- Sent from Gmail for mobile | mobile.google.com Mark J. Reed -- 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/