"catkin --force-color build" doesn't work anymore in some terminals

[neumann89]

System Info

• Operating System: Ubuntu Xenial 4.4.0-51-generic #72-Ubuntu SMP Thu Nov 24 18:29:54 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
• Python Version: 2.7.12
• Version of catkin_tools: 0.4.2
• ROS Distro: kinetic

Expected Behavior

Since switching from Ubuntu Trusty/ROS Indigo to Ubuntu Xenial/ROS Kinetic the --force-color option doesn't work anymore in combination with the build command for embedded terminals as used in Eclipse for example. If I only run "catkin --force-color --test-colors" then I get a colored output.

[wjwwood]

@neumann89 any chance you could retry with 0.4.3? I'm unable to reproduce this by doing these two commands (it works as expected for me):

• catkin build > tmp.txt && cat tmp.txt; rm tmp.txt
• catkin build --force-color > tmp.txt && cat tmp.txt; rm tmp.txt

I'm on Ubuntu 16.04, I ran those in gnome-terminal and I'm using catkin tools version 0.4.3.

[neumann89]

Thanks for your answer @wjwwood!

Now I could reproduce the bug. When I run catkin build --force-color > tmp.txt in gnome-terminal it will create additional symbols like [36mProfile:[0m [33mdefault[0m[0m.

But when I change the order of the parameter to catkin --force-color build > tmp.txt, they are missing.

Edit: I'm also using catkin tools 0.4.3 now

[wjwwood]

It looks like the issue is that the option --force-color for the build verb does not inherit it's default from the --force-color option of the catkin executable. That would explain why catkin build --force-color works but catkin --force-color build does not.