Tomek Szmytka

The new lines are the main part of a workaround that allows `ansicolor` to have its work actually passed on to the log file in the presence of `timestamper` plugin....

> Is there a way to change the behavior if timestamper is not being used? I still get extra lines even if it is not used. The determining factor here...

I actually have been thinking about this for some time but other things always got in the way. This is a new feature that has simply never been implemented. Thank...

@AvihayTsayeg Thanks for the report and the example. I needed to beef it up a little (it had no `ESC` bytes). The issue is fully reproducible. Plugin doesn't kick-in in...

Only now that I have a longer moment I see that the version I could reproduce this in was `ansicolor-0.7.3` - the one still not having #214 . After merging...

Let's stick to comparing apples to apples. 1. Can you please run the example you provided in the issue description? 2. Could you also go to the update center's installed...

Please use example **from the issue description** - the one I updated with ESC bytes (`\033`). At best copy-paste it into a new "Freestyle project" job having only "Color ANSI...

> the result for \033 are just fine. Ok, this means the script you've been using **in issue description** contains control characters that interfere with the whole processing. Here's how...

Luckily github leaves control characters in gists. Both of the invisible characters are `ESC` - this should all be working correctly and indeed is working on any jenkins I've tested...

@AvihayTsayeg > Sent u mail with the complete plugins details Thanks - got it. Feel free to remove your content if you don't want it to hang in the net....