Elegant way to construct a pipeline based on return value and not exit code?
30269
How can I sit in on a stream without getting in the way, while capturing and testing it?
1354
How can I evaluate C# code dynamically?
111721
How to check if gcc has failed, returned a warning, or succeeded in Bash?
99969
Exit Shell Script Based on Process Exit Code
149257
Proper/elegant way of implementing C++ exception chaining?
95926
Can I use pipe output as a shell script argument?
22380
Why does "local" sweep the return code of a command?
152938
How can I run a command if one or more conditions in /execute are satisfied?
128779
How do I get the list of exit codes (and/or return codes) and meaning for a command/utility?
134393
Evaluating the return value of a command line
37287
How to get the return value of a program ran via calling a member of the exec family of functions?
75825
Is there a way of conditionally triggering a compile-time error in verilog?
114527
Reusing pipe data for different commands
130039
Why does using `yes` on bash pipelines *not* cause infinite loops?
99415
Implementing a safe ValueQ that does not evaluate its argument
79805
Which is better, return value or out parameter?
94622
How does one extract a command's exit status into a variable?