Fix: color ascii escapes in json output

[cyanpencil]

Color in comments created some problems in cutter:

Reported by @fcasal (thanks!)

This does not fix 100% of the cases, but 99% of them. (e.g. some ascii escapes will still be seen if a user sets a special vartype comment with Ct containing UTF8 chars in it, but that's pretty rare, and required more major changes, if needed I'll do it in another pr)

[ret2libc]

Is the image taken from before or after the change?

[cyanpencil]

Is the image taken from before or after the change?

Haha, right I should have specified. It is an image of the bug, taken before the changes.

[ret2libc]

How is that after the PR?

[cyanpencil]

Different colors because the first screen was sent to me by @fcasal

[ret2libc]

Oh wow, much better :)

[radare]

btw i was thinking that maybe its time to increase the column where the comments are shown, because it looks pretty bad by default. and… for <80 col terminals we shuold put them on top of the line instead of right by default… but i dont want to make this dynamically defined, so not sure what would be the best solution .. maybe checking at startup time?

…

On 2 Aug 2018, at 16:09, Luca Di Bartolomeo ***@***.***> wrote: <https://user-images.githubusercontent.com/3428362/43588560-09a2a480-966d-11e8-8574-0898dfbf82b9.png> Different colors because the first screen was sent to me by @fcasal <https://github.com/fcasal> — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#10898 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA3-llAPKIUwTY6vOmdfhXiG82NpO89xks5uMwf9gaJpZM4VsQ7x>.

[XVilka]

@radare agree, a good idea.