Skip to content

The switch --no-ansi have no effect #88

Description

@LukeWCS

This is no big thing, but I want to report it also.

If I understand this switch correctly, then it should supress the ANSI color codes. But with active --no-ansi switch, the output is still like this:

`←[37;41m ←[39;49m
←[37;41m Validation: FAILED ←[39;49m
←[37;41m Fatal: 15, Error: 0, Warning: 2, Notice: 0 ←[39;49m
←[37;41m ←[39;49m

←[32mTest results for extension:←[39m
←[33;1mWarning:←[39;22m←[33m Can't detect the file type for .editorconfig, handl
ing it as a binary file.←[39m
←[37;41;1mFatal error:←[39;49;22m←[37;41m Detected windows style newlines instea
d of UNIX newlines in \lukewcs\whowashere\acp\acp_whowashere_info.php←[39;49m
←[37;41;1mFatal error:←[39;49;22m←[37;41m Detected windows style newlines instea
d of UNIX newlines in \lukewcs\whowashere\acp\acp_whowashere_module.php←[39;49m
←[33;1mWarning:←[39;22m←[33m "GPL-2.0" is a deprecated SPDX license identifier,
use "GPL-2.0-only" instead. in \lukewcs\whowashere\composer.json←[39m` ....

I assume ←[32m as example is a ANSI color code?

The full EPV command line in this case is:

php src\EPV.php run --no-ansi --dir "g:\virtual\Users\Test\Documents\GitHub\lf-who-was-here\"

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions