Timeline for How to write an abort-on-error script without adding `|| exit $?` to every line?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 22, 2017 at 11:57 | history | edited | dr_ | CC BY-SA 3.0 |
Fixed formatting
|
| Oct 18, 2012 at 9:44 | comment | added | l0b0 | Make sure to read about the pitfalls. | |
| Oct 17, 2012 at 18:25 | comment | added | dubiousjim |
Note that non-zero return codes only cause a set -e script to fail when the return codes aren't tested. The exact meaning of tested isn't easy to specify, but the basic idea is that failingcmd || nonfailing won't make the whole script fail.
|
|
| Oct 17, 2012 at 11:42 | vote | accept | Tobias Kienzler | ||
| Oct 17, 2012 at 10:39 | comment | added | Chris Card | there you go :) | |
| Oct 17, 2012 at 10:39 | history | edited | Chris Card | CC BY-SA 3.0 |
added 473 characters in body
|
| Oct 17, 2012 at 10:11 | review | Low quality posts | |||
| Oct 17, 2012 at 10:41 | |||||
| Oct 17, 2012 at 10:09 | comment | added | manatwork | Instead of the dummy padding you could quote the documentation. | |
| Oct 17, 2012 at 10:09 | history | answered | Chris Card | CC BY-SA 3.0 |