On 4 February 2013 05:24, Yuri y...@rawbw.com wrote:
On 02/03/2013 03:13, Chris Rees wrote:
I guess this is a cmake/clang port? Cmake, clang and several other
tools give colorised output. This is achieved with escape sequences.
I understand about colorized output.
But aren't such tools
On 3 February 2013 04:14, Yuri y...@rawbw.com wrote:
I redirect the log into the file: portupgrade -a 21 | tee portupgrade.log
However, log still has escape sequences as if it was printed to the
terminal:
^[[0m^[[34m^[[1mGenerating moc_mainwindow.cpp^M
^[[0m^[[34m^[[1mGenerating
On 3 February 2013 04:14, Yuri y...@rawbw.com wrote:
I redirect the log into the file: portupgrade -a 21 | tee portupgrade.log
However, log still has escape sequences as if it was printed to the
terminal:
^[[0m^[[34m^[[1mGenerating moc_mainwindow.cpp^M
^[[0m^[[34m^[[1mGenerating
On 02/03/2013 03:13, Chris Rees wrote:
I guess this is a cmake/clang port? Cmake, clang and several other
tools give colorised output. This is achieved with escape sequences.
I understand about colorized output.
But aren't such tools normally expected to turn colors off when run not
in
I redirect the log into the file: portupgrade -a 21 | tee portupgrade.log
However, log still has escape sequences as if it was printed to the
terminal:
^[[0m^[[34m^[[1mGenerating moc_mainwindow.cpp^M
^[[0m^[[34m^[[1mGenerating subscriptionlistdelegate.moc^M
^[[0m^[[34m^[[1mGenerating
