Hi Jeremy, the difference of this and the tools we already do so is a hard enable vs auto mode.
The cases we already have are handling --color=auto to only add color if running on a terminal. Instead the --color of ip is a hard enable. So if you e.g. do: $ ip --color a > /tmp/foo Or if we would set up an alias $ ip a > /tmp/foo Then the file would contain control chars which no on wants (and could break parsing/monitoring). I checked latest upstream git of iproute and it still is that way. So I'd assume the best would be to file a bug upstream and link it here - what do you think Jeremy? ** Tags added: needs-upstream-report -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1691214 Title: Consider enabling --color by default Status in iproute2 package in Ubuntu: Confirmed Bug description: The output of ip --color a looks a lot nicer to me than ip a If you look in /etc/skel/.bashrc you can see that we already enable color for other commands: alias ls='ls --color=auto' alias grep='grep --color=auto' alias fgrep='fgrep --color=auto' alias egrep='egrep --color=auto' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1691214/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
