Yeah, I had a silly hack for that. I don’t remember what it was. It’s been 3-4 years since I wrote bash for a living. While not perfect, I still need to know if a pipeline command failed. Continuing a script after an invisible error, in many cases, could have been catastrophic.

Woah, that ((i++)) triggered a memory I forgot about. I spent hours trying to figure out what fucked up my $? one day.

When I finally figured it out: “You’ve got to be kidding me.”

When i fixed with ((++i)): “SERIOUSLY! WTAF Bash!”

I was never a fan of set -e. I prefer to do my own error handling. But, I never understood why pipefail wasn’t the default. A failure is a failure. I would like to know about it!

I’ll give you my vim when you pry it from my cold, dead hands.

Hey! I know the guy working on this. Super cool, detail oriented guy.