Kent Fredric posted on Tue, 03 Sep 2013 11:59:13 +1200 as excerpted: > And it is quite simple to remove escape sequences from log files if I > desire it. > > using: app-text/ansifilter > > zcat > /var/log/portage/build/app-accessibility/at-spi2- core-2.6.3:20130825-143158.log.gz > | ansifilter > > using perl and Term::ANSIColor ( standard issue with Perl itself ) > > zcat > /var/log/portage/build/app-accessibility/at-spi2- core-2.6.3:20130825-143158.log.gz > | perl -MTerm::ANSIColor=colorstrip -ple '$_ = colorstrip($_)'
This has long bothered me, but not enough to be worth investigating myself... Zac mentioned in a different subthread that portage's logger is single- threaded ATM, and could become a bottleneck if it had to do too much output processing. How feasible might it be to make something like this a (possibly optional but presumably enabled by default) portage dep, and set portage's default logging to use it when writing the log file (as opposed to the screen output)? Presumably that would pipe to another app to do the actual logfile filtering and writing, so the threading issue would disappear. Actually, presuming there's already a python implementation to parallel that perl one, it's possible the only thing that would need changed would be portage's default logging command. Pythonistas? -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman
