Tomas Janousek wrote:
these three patches have been accepted into RHEL-5.2 and I think they may be
worth including in bash upstream.
+Also, please note that while executing in non-interactive mode and while in
+.I posix
+mode, any special builtin (like \fB.\fP, \fB:\fP, \fBbreak\fP,
+\fBcontinue\fP, \fBeval\fP, \fBexec\fP, \fBexit\fP, \fBexport\fP,
+\fBreadonly\fP, \fBreturn\fP, \fBset\fP, \fBshift\fP, \fBsource\fP,
+\fBtimes\fP, \fBtrap\fP, \fBunset\fP) exiting with a non-zero status
+causes the shell to stop execution.
Doesn't 'exec' replace the process? I get the others (I think), but I
don't understand what shell is left to "stop execution" after an exec.
--
Matthew
HIPPOS wallow slightly in the MUDDY RIVER
What do you want to do next?
> WALLOW IN MUDDY RIVER
You join HIPPOS.
