GNU bug report logs - #30105
Additional "grep" parameter to change the exit code from 1 to 0, even if grep doesn't find pattern

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Vasyl Vavrychuk <vvavrychuk <at> gmail.com>
Subject: bug#30105: closed (Re: bug#30105: Additional "grep" parameter to
 change the exit code from 1 to 0, even if grep doesn't find pattern)
Date: Sun, 14 Jan 2018 17:17:01 +0000

[Message part 1 (text/plain, inline)]

Your bug report

#30105: Additional "grep" parameter to change the exit code from 1 to 0,  even if grep doesn't find pattern

which was filed against the grep package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 30105 <at> debbugs.gnu.org.

-- 
30105: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=30105
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: Vasyl Vavrychuk <vvavrychuk <at> gmail.com>
Cc: 30105-done <at> debbugs.gnu.org
Subject: Re: bug#30105: Additional "grep" parameter to change the exit code
 from 1 to 0, even if grep doesn't find pattern
Date: Sun, 14 Jan 2018 09:16:41 -0800

Vasyl Vavrychuk wrote:
> Actually I use grep in pipe with
> 
>    set -eo pipefail
> 
> but still there I can do
> 
>    ... | grep exrp || test $? -lt 2 | ...
> 
> Thanks for suggestion.

You're welcome. You'll need to parenthesize of course. Closing the bug.

[Message part 3 (message/rfc822, inline)]

From: Vasyl Vavrychuk <vvavrychuk <at> gmail.com>
To: bug-grep <at> gnu.org
Subject: Re: Additional "grep" parameter to change the exit code from 1 to 0, 
 even if grep doesn't find pattern
Date: Sun, 14 Jan 2018 07:21:11 +0200

> > I want to suggest my idea about a additional "grep" parameter which
> > would change the exit code 1 to 0, even when "grep" doesn't find a
> > pattern. I.e. something similar to "-0".
>
> Thanks, but you can avoid triggering your trap
> by appending "|| :" to your grep command.
>
> E.g.,
>
>     grep not-found /dev/null || :
>
> Then, even when grep fails, the shell sees only the successful
> exit code from the ":" (always succeeding) built-in command.

It replaces exit status 2 with success too.
I would like to have an option to return success if nothing is found but
still return fail if error happens.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.