Currently when you supply an invalid cmd or env you get a generic TypeError from inside some Ruby C code that gives you no indication of what you did wrong. This wraps those exceptions in a message that at least tells you what argument you messed up.
Currently when you supply an invalid cmd or env you get a generic TypeError from inside some Ruby C code that gives you no indication of what you did wrong. This wraps those exceptions in a message that at least tells you what argument you messed up.
r? @nelhage