Bug with exit status of zsh -c

Bug with exit status of zsh -c

[Bart Schaefer]

This recently bit me in a procmail recipe.

	zsh -fc '! print several words here | fgrep -i -s -e words'

returns an exit status of zero.  The leading ! should cause it to return a
nonzero exit status.  By contrast,

	bash -fc '! print several words here | fgrep -i -s -e words'

correctly exits with status 1.

This bug affects zsh 3.0.x, 3.1.x, 4.0.x.

Re: Bug with exit status of zsh -c

[Bart Schaefer]

On Aug 13,  6:46pm, Bart Schaefer wrote:
} Subject: Bug with exit status of zsh -c
}
} This recently bit me in a procmail recipe.
} 
} 	zsh -fc '! print several words here | fgrep -i -s -e words'
} 
} returns an exit status of zero.

Is this really all that's necessary?

--- zsh-forge/current/Src/exec.c	Mon Jul  9 09:18:07 2001
+++ zsh-4.0/Src/exec.c	Mon Aug 13 21:54:09 2001
@@ -943,6 +943,8 @@
 
     if (wc_code(code) != WC_PIPE)
 	return lastval = (slflags & WC_SUBLIST_NOT) != 0;
+    else if (slflags & WC_SUBLIST_NOT)
+	last1 = 0;
 
     pj = thisjob;
     ipipe[0] = ipipe[1] = opipe[0] = opipe[1] = 0;

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com

Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net   

Re: Bug with exit status of zsh -c

[Bart Schaefer]

On Aug 14,  4:57am, Bart Schaefer wrote:
}
} Is this really all that's necessary?

Nobody has said "boo" about this one way or the other -- my only worry,
really, is about the cases where last1 is supposed to be set to 2 -- so
I'm going to go ahead and commit it and we just have to be sure that it
has been tested before we release 4.0.3.

(For reference, I'm talking about zsh-workers/15617.)

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com

Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net