Re: failed grep should cause subshell to exit

-David On Mon, Aug 19, 2013 at 3:43 AM, Andreas Schwab wrote: > David Lehmann writes: > > > ! grep hello x > > ! causes the shell to ignore -e. > > Andreas. > > -- > Andreas Schwab, SUSE Labs, sch...@suse.de > GPG Key fingerprint = 0196 BAD8 1CE9 1970

Re: i++ cause bad return code when result is 1

error code. ...IMHO, of course. On Mon, Aug 19, 2013 at 7:40 AM, Greg Wooledge wrote: > On Mon, Aug 19, 2013 at 05:50:31AM +0200, Chris Down wrote: > > On 2013-08-18 16:57, David Lehmann wrote: > > > The ((i++)) fails only when the result is 1. When the result is 0 or >

i++ cause bad return code when result is 1

% uname -a Linux dph1d1ods13 2.6.32-279.2.1.el6.x86_64 #1 SMP Thu Jul 5 21:08:58 EDT 2012 x86_64 x86_64 x86_64 GNU/Linux % bash --version GNU bash, version 4.1.2(1)-release (x86_64-redhat-linux-gnu) The ((i++)) fails only when the result is 1. When the result is 0 or 2, it do

failed grep should cause subshell to exit

### should never see done ** ** % uname -a Linux x 2.6.32-279.2.1.el6.x86_64 #1 SMP Thu Jul 5 21:08:58 EDT 2012 x86_64 x86_64 x86_64 GNU/Linux % bash --version GNU bash, version 4.1.2(1)-release (x86_64-redhat-linux-gnu) ( set -ex ** ** echo hello >x grep hello x