Debug output is not displayed on STDERR

[Yewzir]

What happened?

Currently, warnings and errors are displayed on STDOUT, but I think STDERR is a better choice for this. Colored output is unfortunately problematic in such a case. However, I suspect that colored output is intended, given similar output problems we've encountered in the past.

Current observation on STDOUT

      | �[38;2;255;000;000m┌─ expression started here�[0m
    2 | �[38;2;173;216;230m(�[0mimport std.Sys
    3 |
    4 | # Printing
    5 | �[38;2;144;238;144m(�[0mprint "Hello, World!"�[38;2;144;238;144m)�[0m
      | �[38;2;255;000;000m^�[0m
    6 |
    7 | # Looping
        Missing ')' in import `std.Sys'

Desired expectation on STDERR

      | ┌─ expression started here
    2 | (import std.Sys
    3 |
    4 | # Printing
    5 | (print "Hello, World!")
      | ^
    6 |
    7 | # Looping
        Missing ')' in import `std.Sys'

The most recent tags and base branch are listed below, but I fear the problem is present everywhere.

What ArkScript version are you seeing the problem on?

dev, v4.2.0, v4.1.2, v4.1.1

Operating System

Linux

Compiler used

GCC

Compiler version used

Alpine 15.2.0

Relevant code & log output

Documentation

• I have read existing related documentation before submitting this report
• I have searched for an existing issue before posting

[SuperFola]

Hi there, thanks for the report.

If I understand correctly, you expect colours to be on stderr and diagnostics on stdout? I'm not sure that would make much sense, so I probably misunderstood.

I realise I never documented how to turn colours off in diagnostics, could try defining a shell env var NOCOLOR and see if that fixes it?

Diagnostics check for the presence of such a variable to enable/disable colours (enabled by default).

Happy to come up with another solution if that's not good enough.