This fixes #361

As I mentioned in the other issue, my personal opinion is that this should be the default behavior and there could be a option or setting that switches it to the current behavior. (This underscores the need for a workspace agnostic catkin tools settings, something like ~/.catkin_tools.conf)

Strongly in support of this. Any chance it can target 0.4.3?

I was going to open a new pr that inverts the logic, so that printing stdout was the default behavior and you could configure catkin_tools through a user level config to do the current behavior. However, I haven't had time to do this. Hopefully I'll have a week to catch up on this repository and the others like rvizin the coming month.

Would this address issue #419?

@Levi-Armstrong I believe so.

Would this address issue #419?

@wjwwood I don't think so. #419 will be fixed with #400. This PR collects all output (stdout + stderr) from the process and prints it on stdout, doesn't it?

@rhaschke I think you may be right. I am getting the "how much to print out" versus "where to print what out" confused.