Comment 3 for bug 1996942

Thanks, I committed it.

I think the scripts are meant to fail when anything returns a non-zero exit code; the problem can sometimes be to convince the underlying Lisp to exit with a non-zero code. In the past I have used `clisp -ansi -on-error abort` as the basic invocation of CLISP, and my recollection is that the `-on-error abort` does the right thing: it continues if there is a continue restart, and otherwise exits with an error -- maybe that would help?