[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: grep . /; echo $?
From: |
Bob Proulx |
Subject: |
Re: grep . /; echo $? |
Date: |
Thu, 10 Nov 2005 09:00:03 -0700 |
User-agent: |
Mutt/1.5.9i |
Aharon Robbins wrote:
> My two cents: this isn't worth the trouble. I've written lots of shell scripts
> in my life, and typically all one really wants to know is success/failure:
> ...
> My suggestion is to K.I.S.S.:
>
> EXIT CODE
> 0 - found at least one match
> 1 - found no matches at all
> 2 - something went wrong
I also agree with this sentiment. The above is the useful practical
behavior.
Bob
- Re: grep . /; echo $?, (continued)
- Re: grep . /; echo $?, Julian Foad, 2005/11/04
- Re: grep . /; echo $?, Charles Levert, 2005/11/04
- Re: grep . /; echo $?, Julian Foad, 2005/11/08
- Exit statuses and errors messages (was Re: grep . /; echo $?), Charles Levert, 2005/11/08
- Re: Exit statuses and errors messages (was Re: grep . /; echo $?), Charles Levert, 2005/11/08
- Re: Exit statuses and errors messages (was Re: grep . /; echo $?), Julian Foad, 2005/11/09
- Re: grep . /; echo $?, Benno Schulenberg, 2005/11/04
- Re: grep . /; echo $?, Charles Levert, 2005/11/04
- Re: grep . /; echo $?, Julian Foad, 2005/11/04
Re: grep . /; echo $?, Aharon Robbins, 2005/11/09
- Re: grep . /; echo $?,
Bob Proulx <=